OpenStack - User contributions [en]

NovaVMware/DeveloperGuide

2013-06-28T16:01:46Z

Danwent:

=Developer's DevStack + vSphere Guide=

This is a short guide for developers interested in working on OpenStack and vSphere (ESX, ESXi, and vCenter) drivers.

==vSphere Environment and Inventory==

Set up a vSphere 5.0 (or better) developer's environment. For development purposes, you'll need to have one of these inventory types.

[[File:VCenter trivial inventory.png|framed|none|a trivial Inventory]]

... or ...

[[File:VCenter cluster inventory.png|framed|none|inventory with a DRS cluster]]

Note: The cluster should be DRS enabled with automatic placement turned on. Also, if you can't get two or more ESX hosts to work with, you can still work with one host in the cluster, but you won't be able to observe VM placement behaviors since there won't be anywhere to place the VMs except for the solitary host.

=Development Environment=
== Get an Ubuntu 12.04 (suggested) VM setup==
This Ubuntu workstation can run as a VM itself, but it should have public internet access (ideally direct, but http proxy is workable if you don’t need to commit code back to OpenStack if you do, see the troubleshooting page for steps that ''may'' help). It should also have a reasonably high bandwidth link to the the vSphere hosts, as it will need to stream images from the Ubuntu workstation to the vSphere host.

We suggest your Ubuntu workstation have
* at least 10 GB disk, with 20+ GB being ideal.
* at least one vCPU, with 2 being ideal.
* 4 GB of RAM.

==install Devstack (http://devstack.org/) in your new VM==
Once booted, run:
sudo apt-get install git
git clone http://github.com/openstack-dev/devstack.git
cd devstack

=Setup localrc for DevStack=
create a file named “localrc” in your devstack directory with the content shown below (for each item with $variable_name, you will need to enter values specific to your environment, the rest you can just leave as is).

file ~/devstack/''localrc''
ENABLED_SERVICES=g-api,g-reg,key,n-api,n-crt,n-cpu,n-net,n-cond,n-sch,rabbit,mysql,horizon
VIRT_DRIVER=vsphere
VMWAREAPI_IP='''$your_vCenter_ip_address'''
VMWAREAPI_USER=root
VMWAREAPI_PASSWORD='''$password_goes_here'''
VMWAREAPI_CLUSTER='''$your_cluster_name'''
DATABASE_PASSWORD=nova
RABBIT_PASSWORD=nova
SERVICE_TOKEN=nova
SERVICE_PASSWORD=nova
ADMIN_PASSWORD=nova
FLAT_INTERFACE=tapfoo
HOST_IP='''$your_development_vm_ip'''

Note: omit the line ''VMWAREAPI_CLUSTER'' if you are using the ''trivial'' inventory example.

=start stack (first time)=
./stack.sh
This will take a long time the first time, as it pulls down all code and dependencies.
Note: may fail on first start.

=Credentials and Environment Variables=
get the OpenStack API credentials in your environment variables:

$ source openrc demo demo

This is needed anytime you make a call using an openstack CLI client like ‘nova’, ‘glance’, or ‘quantum’. You can rerun this at any time from the devstack directory if you need to re-login in at a later point.

=Glance Initial Setup=
Get a VMDK to use as a disk image and upload it to OpenStack using the Glance API.

==Get an initial VMDK to work with==
There are a lot of “gotchas” around what VMDK disks work with OpenStack + vSphere, so we strongly suggest using the provided image to start. In the Appendix there is information about creating/converting your own images.

download the image 1 GB debian disk image (user/password to login this image after booting is nicira/nicira).
https://www.dropbox.com/s/utvri5bw3zztty6/Debian-flat.vmdk

Place the file under your home directory <code><nowiki>~/</nowiki></code>

==Upload your VMDK to glance==

$ glance add name="Debian" disk_format=vmdk container_format=bare is_public=true \
--property vmware_disktype="preallocated" < ~/Debian-flat.vmdk
... or ...
$ glance image-create --name Debian --is-public=True --container-format=bare \
--disk-format=vmdk --property vmware-disktype="preallocated" < ~/Debian-flat.vmdk

This will print out an <image-id> for use below. If you forget it, you can always run “glance image-list” to see all existing images.

=Nova Boot=
boot a VM using the “<image-id>” from above

$ nova boot --image <image-id> --flavor 1 test1

Now you can interact with the image using other nova client commands.
For example
$ nova list
+--------------------------------------+-------+--------+------------+-------------+------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+------------------+
| 9bb724bf-298d-4a63-a653-dab7fcbd9ac7 | test1 | ACTIVE | None | NOSTATE | private=10.0.0.2 |
+--------------------------------------+-------+--------+------------+-------------+------------------+

Note: if your disk is big, it can take a VERY long time to stream the image from glance to your datastore (e.g., ~7 minutes for a 1 GB thick image). This will happen only the first time a new image UUID is used on a datastore. You can monitor progress by viewing the size of the file in the vmware_base directory of the filestore.

Once this is done, you can view the VM using vCenter. The username/password for the above Debian image is nicira/nicira .

You can access the OpenStack Web GUI (called horizon) by accessing your Ubuntu host on port 80, though currently VNC access via Horizon is broken (see: https://review.openstack.org/#/c/30036/ for a patch to fix this).

=Using Screen=
Use screen to interact with individual openstack services

$ screen -x stack

See: http://www.gnu.org/software/screen/manual/screen.html <- for how to use

* "Control + a" enters command mode... enter this for each new command character
characters 0 through 9 switch tabs
** the 'd' character detaches the session
** the '[' character enters "copy mode" which allows you to navigate the screen trace and 'escape' escapes the copy mode.

=Working the Development Environment=
If you want to reset your environment, run:
./unstack.sh
./stack.sh

* This run of stack.sh will be faster (~1 minute) as it resets all database and service state, but does not need to re-download packages or source code.
* After running ./unstack be sure to clean out all your datastores and delete any files left behind on accident. This will prevent a great number of problems people won't see in production environments. (For example: partially uploaded VMDK.)

Note: the source code is not automatically updated when you reset your environment. This is valuable, as you can manage your source code manually via git, having many branches, etc.

=Testing=
==Install python support libraries==
===apt-get libs===
$ sudo apt-get install python-dev libmysqlclient-dev python-pip build-essential
$ sudo apt-get install libxml2-dev libxslt1-dev

===pip based tool installs===
$ sudo pip install --upgrade pip
$ sudo pip install --upgrade virtualenv
$ sudo pip install MySQL-python
$ sudo pip install tox
$ sudo pip install python-subunit

====pip proxy troubleshooting====
If you get connection refused here - try this
export PIP_INDEX_URL="http://pypi.openstack.org/openstack"

====Install OpenStack libs====
$ cd /opt/stack/nova
$ sudo pip install -i http://pypi.openstack.org/openstack -r requirements.txt -r test-requirements.txt

Note: make sure everything in the requires lists gets installed. Some installers have individual issues that you may have to clear one at a time. In particular lxslt has some issues that may require attention to properly clear.

==Using TOX for testing==
See: https://wiki.openstack.org/wiki/ProjectTestingInterface

Important tests to run before submitting for code review are
tox -e py27
tox -e pep8

==Code Coverage tests and information==
cd nova
tox -e cover (code coverage)

look under the cover directory for html reports on the code coverage for that module. The file index.html contains the overall coverage report

NOTE: tests may run 10, 20, or as long as 65 minutes (depending on your hardware, network, and system) and produce no output until they complete. This is normal. You system may become sluggish but should not lock up entirely, a system hang can be symptomatic of an improperly configured test environment. Tests will run on Mac OSX. 2 Cores with 2GB of RAM on an Ubuntu 12.04 machine that is properly configured should take between 10 and 20 minutes to complete.

==Additional setup==
If you are on Ubuntu 12.04 and need to use Python 2.6 (which OpenStack needs for some test scripts) install the old version of python by doing the following:

$ sudo add-apt-repository ppa:fkrull/deadsnakes
$ sudo apt-get update
$ sudo apt-get install python2.6 python2.6-dev

=Troubleshooting=
''Some workplaces may have to use special networking and/or proxy settings and that these may change when you are mobile. Those issues can cause problems with apt-get, git and other parts of OpenStack. If you are in a place that needs special proxy rules, [https://help.ubuntu.com/community/AptGet/Howto/#Setting_up_apt-get_to_use_a_http-proxy setup apt-get with a proxy]. You may also have to set [http://askubuntu.com/questions/158557/setting-proxy-from-terminal other proxy settings] depending on your company's particular firewall rules.''

== Logging ==
You may have a situation where you need to monitor devstack's log files. Here's how you set up logging to file with the least amount of fuss.

To set up logging of screen windows set the shell variable SCREEN_LOGDIR to the directory you want the log files to go. Log files will appear with names like ''screen-$SERVICE_NAME-$TIMESTAMP.log'' in that dir and symbolic link screen-$SERVICE_NAME.log will link to the latest log file. Logs are kept for as long specified in the LOGDAYS variable.

Both SCREEN_LOGDIR and LOGDAYS are shell variables so you need to set them either in your shell or in localrc. Use shell commands if you only want the logs to work this one time. Use ''localrc'' if you always want to have log files appear.

Assuming you have already made a directory...

$ mkdir ~/log

Then, if you only want logs this one time, in your bash shell say...

$ export SCREEN_LOGDIR=~/log
$ export LOGDAYS=2

... or if you ''always'' want log files, in your localrc add the lines ...

SCREEN_LOGDIR=~/log
LOGDAYS=2

The stack.sh script will automatically rotate the log files for you.

== MySQL issues ==
If you get stuck with Keystone try...
$ mysql -u root -pnova
... if that doesn't work you probably have a broken mysql install. If you have problems getting mysql to behave, try purging the OpenStack version of the install and install the database manually. Here’s how to rip everything down and install mysql-server from scratch yourself.

$ ./unstack
$ sudo apt-get purge mysql-server
... you may need to use the name mysql-server-5.5 instead ...
$ sudo apt-get autoremove
$ sudo apt-get install mysql-server-5.5
$ sudo mysql_install_db
$ sudo mysqladmin -u root password 'nova'
$ sudo service mysql restart
$ ./stack

== Keystone Issues ==
If you get stuck when you are checking your keystone connection via curl then it’s your proxy settings. Try setting the following in /etc/environment
no_proxy=localhost,127.0.0.0/8,127.0.1.1,127.0.1.1*,local.home

== General Database Issues ==
If you have trouble with testing or other database heavy activities you may need to follow:
http://codeinthehole.com/writing/how-to-set-up-mysql-for-python-on-ubuntu/

== rootwrap Issues ==
If networking suddenly stops working with an error like this

Traceback (most recent call last):
File "/usr/bin/nova-rootwrap", line 59, in <module>
from nova.rootwrap import wrapper
ImportError: No module named rootwrap

Then something has added a broken rootwrap to /usr/bin. Remove the /usr/bin/nova-rootwrap and it will use the correct one in /usr/local/bin

=Appendix=
==Converting Images==
# Download fresh Precise cloud image from: http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img
# Convert to VMDK using "qemu-img convert". For example <br /><code><nowiki> qemu-img convert -f raw ~/Downloads/precise-server-cloudimg-amd64-disk1.img -O vmdk precise-server-cloudimg-amd64-disk1.vmdk</nowiki></code>
# Convert your existing vmdk from sparse to thick using vmware CLI

Note: this is currently required, due to a bug we are investigating.

Once you have rCLI installed on your Ubuntu box you can follow the instructions in the link below. You can download rCLI from vmware.com. Go to vSphere downloads on the drivers and tools tab. The latest version from the date this was written is 5.1 and the link is here. You may need to install perldoc and other required libraries but the installer will tell you what to do.

Link to converting sparse vmdk files to thick -
http://www.cosonok.com/2010/08/using-vmware-vsphere-cli-to-convert.html

For example - create the new vmdk, rename the old, rename the new to the old name

vmkfstools --server=10.20.120.61 -i /vmfs/volumes/storage1/testVM/testVM.vmdk /vmfs/volumes/storage1/testVM/testVM_thick.vmdk

vmkfstools --server=10.20.120.61 -E /vmfs/volumes/storage1/testVM/testVM.vmdk /vmfs/volumes/storage1/testVM/testVM_sparse.vmdk

vmkfstools --server=10.20.120.61 -E /vmfs/volumes/storage1/testVM/testVM_thick.vmdk /vmfs/volumes/storage1/testVM/testVM.vmdk

HypervisorSupportMatrix

2013-05-07T06:17:08Z

Danwent: /* Hypervisor support matrix */

= Hypervisor support matrix =

This is an attempt to help new users decide on a hypervisor based on features that can be controlled through compute.

Most [[OpenStack]] development is done with the KVM and XEN hypervisors. This means that (currently at least) you are more likely to find community support for issues with these hypervisors. All features that are currently supported in KVM are also supported in QEMU.

As far as the Xen hypervisor is concerned, it is worth noting the following definitions:

* [[XenServer]]: Commercial, supported product from Citrix.
* Xen Cloud Platform (XCP): Open-source equivalent of [[XenServer]] (and the development project for the toolstack). Everything said about [[XenServer]] below applies equally to XCP.
* XenAPI: The management API exposed by [[XenServer]] and XCP.
* XAPI: The primary daemon on [[XenServer]] and Xen Cloud Platform; the one that exposes the XenAPI.

Nova has support for [[XenServer]] and XCP through the XenAPI virt layer. Note that this does not imply support for other Xen-based platforms such as those shipped with RHEL 6 or SUSE, which is provided via the libvirt layer.

Please help keep this list up-to-date.

'''Legend''': ✔ indicates support, ✗ indicates the feature is not supported, G indicates the feature will be added in Grizzly, * indicates there is a caveat to the functionality (caveats need to be documented!), and a blank cell generally indicates more testing is needed to make a judgment.

{| border="1" cellpadding="2" cellspacing="0"
| '''Feature'''
| '''[[XenServer|XenServer/XCP]] '''
| '''[http://docs.openstack.org/trunk/openstack-compute/install/yum/content/kvm.html KVM]'''
| '''[http://docs.openstack.org/trunk/openstack-compute/install/yum/content/qemu.html QEMU]'''
| '''[http://lxc.sourceforge.net LXC]'''
| '''[http://docs.openstack.org/trunk/openstack-compute/admin/content/vmware.html ESXi/VC]'''
| '''[[Hyper-V]]'''
| '''[[Baremetal]]'''
| '''[https://blueprints.launchpad.net/nova/+spec/powervm-compute-driver PowerVM]'''
|-
| Launch
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Reboot
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Terminate
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Resize
| ✔
| ✔
| ✔
|
|
| ✔
|
| ✔
|-
| Rescue
| ✔
| ✔
| ✔
|
| ✔
|
|
| ✗
|-
| Pause
| ✔
| ✔
| ✔
|
| ✗
| ✔
|
| ✗
|-
| Un-pause
| ✔
| ✔
| ✔
|
| ✗
| ✔
|
| ✗
|-
| Suspend
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✗
|-
| Resume
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✗
|-
| Inject Networking
| ✔*(1)(2)
| ✔*(1)
| ✔*(1)
|
| ✔*
| ✔
| ✔
| ✗
|-
| Inject File
| ✔
| ✔*
| ✔*
|
|
| ✗*(6)
| ✔
| ✗
|-
| Serial Console
| ✗*(4)
| ✔
| ✔
| ✗
| ✔
| ✗
| ✔*
| ✗
|-
| VNC Console
| ✔*(5)
| ✔*
| ✔*
|
| ✔
|
|
| ✗
|-
| Attach Volume
| ✔
| ✔
| ✔
| ✗
| ✔
| ✔
|
| ✗
|-
| Detach Volume
| ✔
| ✔
| ✔
| ✗
| ✔
| ✔
|
| ✗
|-
| Live Migration
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✗
|-
| Snapshot
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✔
|-
| iSCSI
| ✔
| ✔

| ✔
|
| ✔
| ✔
|
|
|-
| Set Admin Pass
| ✔
| ✗
| ✗
|
| ✗
| ✗*(6)
|
| ✗
|-
| Get Guest Info
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✔
|-
| Get Host Info
| ✔
| ✔
| ✔
|
| ✔
| ✔
|
| ✔
|-
| Glance Integration
| ✔
| ✔
| ✔
|
| ✔
| ✔
| ✔
| ✔
|-
| Service Control
| ✔
| ✔
| ✔
|
| ✔
|
|
| ✗
|-
| VLAN Networking
| ✔
| ✔
| ✔
| ✔
| ✔
| ✗*(7)
|
| ✗
|-
| Flat Networking
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Security Groups
| ✔
| ✔
| ✔
| ✔
| ✗*(9)
|
|
| ✗
|-
| Firewall Rules
| ✔
| ✔
| ✔
|
|
|
|
| ✗
|-
| Routing
| ✔
| ✔
| ✔
|
| ✔
| ✗*(7)
|
| ✗
|-
| nova diagnostics
| ✔
| ✔
| ✔
|
|
|
|
| ✗
|-
| Config Drive
| ✔*(3)
| ✔
| ✔
| ✔
|
| ✔
|
| ✗
|-
| Auto configure disk
| ✔
|
|
|
|
|
|
| ✗
|}

# Inject Networking only works with nova-network in Flat mode, and only with Debian/Ubuntu based virtual machines, and only at boot time
# [[XenServer]] integration also supports using a guest agent to inject networking settings, at any time when a VM has the guest agent installed, through an admin API extension
# XenAPI Config drive support [https://blueprints.launchpad.net/nova/+spec/xenapi-config-drive was added in Grizzly]
# XenAPI support for serial console is currently [https://review.openstack.org/#/c/17959/ under development]
# Unknown: VNC support has since [https://blueprints.launchpad.net/nova/+spec/vnc-console-cleanup been unified between libvirt and XenAPI]
# Functionality provided by cloudbase-init for windows http://www.cloudbase.it/cloud-init-for-windows-instances/
# Vlan and Routing is supported on Hyper-V when using the Quantum Hyper-V Plugin
# Support of Xen using Libvirt
# Security Groups supported on VC/ESX Driver when using the Quantum NVP Plugin

== Description of features ==

=== nova diagnostics ===

The `nova diagnostics` command will provide some information about resource use associated with an instance. See the [http://docs.openstack.org/folsom/openstack-compute/admin/content/diagnose-compute-tutorial.html OpenStack Compute admin guide] for more details.

=== Auto configure disk ===

Automatically reconfigure the size of the partition to match the size of the flavor's root drive before booting.

== Known bugs, by hypervisor ==

* [https://bugs.launchpad.net/nova/+bugs?field.tag=kvm KVM-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver,xen Xen-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=qemu QEMU-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc LXC-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware VMware-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=hyperv Hyper-V-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=baremetal Baremetal-specific bugs]
* [https://bugs.launchpad.net/nova/+bugs?field.tag=powervm PowerVM-specific bugs]

NovaVMware

2013-04-25T17:46:11Z

Danwent: /* Unit Tests */

This is the sub-team page for those working on the VMware driver in Nova.

= Open Development Items =

===Devstack===
* Basic devstack patch is in review: https://review.openstack.org/#/c/27440/
* Still need get an image that is automatically downloaded and added to glance.

===Bugs===
* https://bugs.launchpad.net/nova/+bugs?field.tag=vmware

===Proposed Blueprints===
* https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service
* https://blueprints.launchpad.net/nova/+spec/fc-support-for-vcenter-driver
* https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler
* https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver
* https://blueprints.launchpad.net/nova/+spec/esx-resource-pools-as-compute-nodes

= Open Testing Items =

===Unit Tests===

Coverage needs a lot of help, see: [[File:NovaVMwareUnitTestCoverage.png|NovaVMwareUnitTestCoverage.png]]

===System Tests===
* Need to explore running tempest tests with vSphere driver.

= Open Documentation Items =
* Documentation has not yet been updated for Grizzly. Thus, it is way out of date and unusable.

NovaVMware

2013-04-25T17:45:43Z

Danwent: /* Unit Tests */

This is the sub-team page for those working on the VMware driver in Nova.

= Open Development Items =

===Devstack===
* Basic devstack patch is in review: https://review.openstack.org/#/c/27440/
* Still need get an image that is automatically downloaded and added to glance.

===Bugs===
* https://bugs.launchpad.net/nova/+bugs?field.tag=vmware

===Proposed Blueprints===
* https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service
* https://blueprints.launchpad.net/nova/+spec/fc-support-for-vcenter-driver
* https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler
* https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver
* https://blueprints.launchpad.net/nova/+spec/esx-resource-pools-as-compute-nodes

= Open Testing Items =

===Unit Tests===

Coverage needs a lot of help, see: NovaVMwareUnitTestCoverage.png

===System Tests===
* Need to explore running tempest tests with vSphere driver.

= Open Documentation Items =
* Documentation has not yet been updated for Grizzly. Thus, it is way out of date and unusable.

File:NovaVMwareUnitTestCoverage.png

2013-04-25T17:45:03Z

Danwent: Danwent moved page File:Screen Shot 2013-04-25 at 10.21.21 AM.png to File:NovaVMwareUnitTestCoverage.png

File:Screen Shot 2013-04-25 at 10.21.21 AM.png

2013-04-25T17:45:03Z

Danwent: Danwent moved page File:Screen Shot 2013-04-25 at 10.21.21 AM.png to File:NovaVMwareUnitTestCoverage.png

#REDIRECT [[File:NovaVMwareUnitTestCoverage.png]]

2013-03-18T21:30:01Z

2013-03-18T18:28:37Z

Danwent: /* DB (markmcclain) */

2013-03-04T20:48:00Z

Danwent: /* RC1 Feature Freeze Exceptions (danwent) */

{{:Network/Header}}

The OpenStack Quantum Team holds public meetings in <code><nowiki>#openstack-meeting</nowiki></code>. Everyone is encouraged to attend.

== Apologies for Absence ==
* --[[User:Danwent|danwent]] ([[User talk:Danwent|talk]]) 19:50, 25 February 2013 (UTC)

== Agenda for Next Quantum Team Meeting ==

=== Announcements / Reminders: ===
* --[[User:Danwent|danwent]] ([[User talk:Danwent|talk]]) 05:20, 4 March 2013 (UTC)
* G-RC1 branch date targeted at March 12th (one week away!).
* Starting tuesday (tomorrow) bar for bugs will increase to high priority fixes only (similar to what would be required for getting into stable branch). Bugs must fix something that is truly broken.

=== RC1 Feature Freeze Exceptions (danwent) ===
* --[[User:Danwent|danwent]] ([[User talk:Danwent|talk]]) 05:24, 4 March 2013 (UTC)
* Both FFEs are in and merged. Great work team!
* For LBaaS: still reviewing devstack support: https://review.openstack.org/#/c/23382/ (old review https://review.openstack.org/#/c/22937/ )
* For multi-agent tracking bug related to handling "state-report" capability of agents: https://review.openstack.org/#/c/23396/

=== RC1 Bugs (markmcclain) ===
*--[[User:Danwent|danwent]] ([[User talk:Danwent|talk]]) 05:32, 4 March 2013 (UTC)
* 14 bugs, all but one in review.
* we should make sure we have core dev tracking each one.
* https://launchpad.net/quantum/+milestone/grizzly-rc1
* Floating IP definition. not currently assigned to RC1, but worth mentioning: https://bugs.launchpad.net/quantum/+bug/1138730

=== Quantum Python-Client (gongysh, markmcclain): ===
* Last Updated: --gongysh 06:12, 4 March 2013 (UTC)
** 2.1.2 is pushed due to the Pyparsing version problem and development needs
** 2.2.0 will be pushed after Quantum Server RC1 is finished
** https://launchpad.net/python-quantumclient/+milestone/2.2 is done
** Need to add some documents for quantum client operation change before 2.2 milestone is released
* [https://launchpad.net/python-quantumclient/+milestone/3.0.0 3.0.0 Milestone] Delayed until after 2.2.0 release.
** [https://blueprints.launchpad.net/python-quantumclient/+spec/pythonic-client Make QuantumClient library more pythonic]
* Topics
** Support Passing 'None' in qunatumclient
** http://lists.openstack.org/pipermail/openstack-dev/2013-February/thread.html#5392
** (Related Abandoned review) https://review.openstack.org/#/c/17436/

=== Documentation (danwent) ===
* [[ Network/GrizzlyDocImpact ]]

=== Quantum work in Horizon (amotoki) ===
* Last Updated: [[User:Amotoki|amotoki]] ([[User talk:Amotoki|talk]]) 13:19, 25 February 2013 (UTC)
* Horizon rc1 : https://launchpad.net/horizon/+milestone/grizzly-rc1
* Grizzly FFE
** https://blueprints.launchpad.net/horizon/+spec/quantum-lbaas (KC) : depends on Quantum LBaaS progress. Need feedback from LBaaS team before merging the patch.
* Bugs related to Quantum
** https://bugs.launchpad.net/horizon/+bugs?field.tag=quantum

=== Open Discussion ===

== Previous meeting logs ==
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/quantum/ here].
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D 2013]
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D 2012]
* Older meeting notes are here: ../MeetingLogs.