OpenStack - User contributions [en]

Neutron/LBaaS/HowToRun

2016-03-18T18:28:29Z

Doug Fish: Update the single line server example to include content-length header

== Getting the Code ==

LBaaS introduces changes in the following modules: (currently all changes are in master branch)

* neutron
* python-neutronclient
* horizon
* devstack

== Devstack Setup ==

Add the following lines to your localrc:
<pre>enable_plugin neutron-lbaas https://github.com/openstack/neutron-lbaas.git
</pre>
<pre>enable_plugin octavia https://github.com/openstack/octavia.git
</pre>
<pre>ENABLED_SERVICES+=,q-lbaasv2
</pre>
<pre>ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api
</pre>

Then run stack.sh

After stack.sh completes you'll be able to manage your Load Balancer via the CLI tools and within Horizon

==Ubuntu Packages Setup==

Install octavia with your favorite distribution:

<pre>pip install octavia </pre>

And edit the service_plugins in [DEFAULT] section in neutron.conf to enable the service:
<pre>sudo sed -i.bak "s/\#\ service_plugins\ \=/service_plugins = neutron.plugins.services.agent_loadbalancer.plugin.LoadBalancerPluginv2/g" /etc/neutron/neutron.conf</pre>

Finally enable the Load Balancer section in Horizon by editing <pre>/etc/openstack-dashboard/local_settings.py</pre> and changing:

<pre>
OPENSTACK_NEUTRON_NETWORK = {
'enable_lb': False
}
</pre>

to

<pre>
OPENSTACK_NEUTRON_NETWORK = {
'enable_lb': True
}
</pre>

Once done restart your Neutron services and Apache to start using.

== Topology Setup ==

Spin up three VMs, two to be servers, and one to be a client.

<pre>nova boot --image <image-uuid> --flavor 1 server1
nova boot --image <image-uuid> --flavor 1 server2
nova boot --image <image-uuid> --flavor 1 client</pre>

Get the UUID of the private subnet.

<pre>neutron subnet-list</pre>

Created a Loadbalancer:

<pre>neutron lbaas-loadbalancer-create --name lb1 private-subnet</pre>

Create a Listener:

<pre>neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP --protocol-port 80 --name listener1</pre>

Create a Pool:

<pre>neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1 --protocol HTTP --name pool1 </pre>

Create Members (using the IPs of server1 and server2):
<pre>
neutron lbaas-member-create --subnet private-subnet --address <server1-ip> --protocol-port 80 pool1
neutron lbaas-member-create --subnet private-subnet --address <server2-ip> --protocol-port 80 pool1</pre>

Create a Healthmonitor and associated it with the pool:

<pre>neutron lbaas-healthmonitor-create --delay 3 --type HTTP --max-retries 3 --timeout 3 --pool pool1</pre>

note the address for use below.

== Validation ==

We now have two hosts with a load balancer pointed at them, but those hosts are not serving up any HTTP content.

A simple trick is to use netcat on the hosts to implement a simple webserver. For example, run:

<pre>while true; do echo -e 'HTTP/1.0 200 OK\r\nContent-Length: 8\r\n\r\n<servername>' | sudo nc -l -p 80 ; done </pre>

replacing <servername> with "server1" and "server2" as appropriate. Once the server is started, you'll see incoming HTTP GET requests.. that's the load balancer health check in action!

If you have python installed, you can also create an index.html with the text "server1" or "server2" then in the same directory run

<pre>sudo python -m SimpleHTTPServer 80</pre>

Finally, to test real load balancing, from your client, use wget to make sure your requests are load-balanced across server1 and server2 as expected.

<pre>wget -O - http://<server1-ip>
wget -O - http://<server2-ip> </pre>

Then use wget to hit the load balancer IP(VIP IP) several times in succession. You should bounce between seeing server1 and server2.

<pre>wget -O - http://<vip-ip>
wget -O - http://<vip-ip>
wget -O - http://<vip-ip>
wget -O - http://<vip-ip> </pre>

If you get some trouble to curl vip-ip, can try the following method:
<pre>sudo ip netns list
qdhcp-xxx
qrouter-xxx
</pre>
<pre>sudo ip netns exec qrouter-xxx curl -v <vip-ip> </pre>

Full list of LBaaS CLI commands is available at [[Quantum/LBaaS/CLI]]

== Troubleshooting ==

LBaas is implemented similar to L3 + DHCP using namespaces. You can use "ip netns list" to find the namespace named qlbaas-<pool_id>, and then test connectivity from that namespace.

Use "screen -x stack" to view the q-svc ,q-lbaas, o-cw, o-api tabs for errors.

Grep syslog for "Octavia" to see messages from Octavia (though they are quite cryptic!)

Sprints/HorizonMitakaSprint

2016-01-05T14:44:45Z

Doug Fish: /* Registration */

The Horizon team is having their Mitaka mid-cycle/sprint in Hillsboro, Oregon.

* Where: Intel - Jones Farm 1, NE Griffin Oaks St, Hillsboro, OR 97124
* When: February 23-25, 2016

=== Travel ===
* Fly into Portland International Airport (PDX)
** Time to drive is approximately 40 minutes
** Trains from airport to Hillsboro are available, but will take approximately 2 hours travel time.

=== Hotels ===
Recommended hotels in Hillsboro are:
* Holiday Inn Express Portland West/Hillsboro , 5900 NE Ray Cir, Hillsboro, OR 97124, Phone:(503) 844-9696
http://www.ihg.com/holidayinnexpress/hotels/us/en/hillsboro/pdxhi/hoteldetail/directions
* Larkspur Landing in Hillsboro, Oregon, 3133 NE Shute Rd, Hillsboro, OR 97124, Phone:(503) 681-2121
http://www.larkspurhotels.com/hillsboro/amenities/?gclid=COeFrZG77ckCFYpffgodyugJvQ
* More hotel options are available Portland as well. Hillsboro is approximately 30 minutes west of downtown Portland.

=== Registration ===
{| class="wikitable sortable"
|-
! # !! Name !! IRC Nick !! Comment !! Email
|-
| 1 || David Lyle || david-lyle || || dklyle0 AT gmail DOT com
|-
| 2 || Richard Jones || r1chardj0n3s || || r1chardj0n3s AT gmail DOT com
|-
| 3 || Diana Whitten || hurgleburgler || || hurgleburgler AT gmail DOT com
|-
| 4 || Tyr Johanson || tyr || || tyr AT hpe DOT com
|-
| 5 || Doug Fish || doug-fish || || drfish AT ibm DOT com
|-
| 6 ||  ||  ||  || 
|}

Horizon/WeeklyBugReport

2015-11-12T16:48:31Z

Doug Fish:

== Weekly Bug Report (Updated 2015-11-09) ==

=== Blueprint Patches ===

* [jpomeroy] Support angular workflow extension as a feature plugin https://review.openstack.org/#/c/214306
* [tqtran] Adding CREATE action to identity users panel https://review.openstack.org/#/c/222297
* [hurgleburgler] Dropdowns should have a consistent design https://review.openstack.org/#/c/232734 (merged)

=== Bugs ===

* [Critical] [tqtran] Missing documentation for plugins https://bugs.launchpad.net/horizon/+bug/1511593
* [High] "Volumes" tab doesn't show up if cinder v1 isn't registered https://bugs.launchpad.net/horizon/+bug/1415712
* [High] [fnordahl] Unable to create subnet from IPv6 subnetpool https://bugs.launchpad.net/horizon/+bug/1498926
* [High] [hurgleburgler] Material Design Theme Needs to Pad the Content Correctly https://bugs.launchpad.net/horizon/+bug/1508692 (merged)
* [Medium] [rajatvig] hz-magic-search-bar does not honor isServer property https://bugs.launchpad.net/horizon/+bug/1496627
* [Low] Launch instance from Volumes Page opens LEGACY launch instance, even if LEGACY is set to False in local_settings https://bugs.launchpad.net/horizon/+bug/1491645

=== About ===

A short weekly summary of blueprints and bugs that are currently of key importance to Horizon. This is to help those short on review time scope their time effectively, or give newcomers a quick list of priority patches to look at.

Criteria:
* Bugs should have submitted patches, or active discussion around the solution. This report is for showing solutions, not discussing validity of new bug reports. The patches should also be in a relatively good state (i.e. passing Jenkins, not stale)
* Patches should be based around the current cycles priorities (https://etherpad.openstack.org/p/mitaka-horizon-priorities)
* For blueprints, list a specific patch rather than the entire blueprint. It is unlikely an entire feature will be merged in a week, but focusing on a single patch is reasonable
* Add IRC handles if possible, to aid communication

Horizon/WebAccessibility

2015-10-07T13:00:02Z

Doug Fish:

* What do we mean by accessibility?
** http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
** http://www.w3.org/TR/WCAG20/
** http://www-03.ibm.com/able/guidelines/web/accessweb.html This IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.

* Testing Techniques
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface. You should be able to reach and activate all of Horizon's functions this way. You should always be able to see the focus. The tabbing should happen in a logical order. I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.

http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast). Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users. Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.

* WAI-ARIA
WAI-ARIA is a specification that lets rich web applications (Like the Horizon Dashboard!) specify the meaning of HTML elements when they are used in a manner that isn't automatically implied by the tag being used. So if you are displaying a button and you are using a <button> or <input type="button"> html element no extra work is needed. However, if you are displaying a button and its constructed out of <div> elements you're going to need to use WAI-ARIA tagging so that assistive technology - especially screen readers can use it. Here's a useful introduction: http://rawgit.com/w3c/aria-in-html/master/index.html

Consider using https://docs.angularjs.org/api/ngAria for angular based code (or all?)

* Screen readers
I'm still looking into screen readers that will be useful in our environments. I'm thinking specifically of
** http://www.nvaccess.org/
** https://wiki.gnome.org/Projects/Orca

* Underlying components
One of our challenges with Horizon is that some of the components we build on may not be accessible. This will likely show up more clearly in our testing with keyboard + screen readers. I expect the process will be that we will find some problem. We willl look at where the improper markup/CSS is generated, and find its not generated directly by Horizon but maybe by django, bootstrap, or some other outside code.

I see that bootstrap claims accessibility (well bootstrap 3 does anyway) [http://getbootstrap.com/getting-started/#accessibility] but I find it curious that there is a bootstrap accessibility plugin [https://www.paypal-engineering.com/2014/01/28/bootstrap-accessibility-plugin-making-the-popular-web-development-framework-better]. Not sure if we are going to need it.

Our calendar widget is clearly not accessible. (I think this widget has i18n problems too)

For each component we find problems in we'll have to determine if there is another suitable component that supports accessibile, if we can workaround the problem, or if this is best handled by contributing to the component itself.

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

CrossProjectLiaisons

2015-10-05T20:25:25Z

Doug Fish:

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || ||
|-
| Glance || Louis Taylor || kragniz
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || Lin Tan || lintan
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachyshka
|-
| Nova || Victor Stinner|| haypo
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Sergey Reshetnyak || sreshetnyak
|-
| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Cinder || Mike Perez || thingee
|-
| Swift || John Dickinson || notmyname
|-
| Neutron || Kyle Mestery || mestery
|-
| Keystone || Morgan Fainberg || morganfainberg
|-
| Horizon || David Lyle || david-lyle
|-
| Glance || Nikhil Komawar || nikhil_k
|-
| Ceilometer || gordon chung || gordc
|-
| Heat || Angus Salkeld || asalkeld
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Trove || Nikhil Manchanda || SlickNik
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Zaqar || ||
|-
| Designate || ||
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Manila || Ben Swartzlander || bswartz
|-
| Murano || Serg Melikyan || sergmelikyan
|-
| Congress || Tim Hinrichs || thinrichs
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Matt Riedemann || mriedem
|-
| Cinder || ||
|-
| Swift || ||
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Keystone || David Stanek || dstanek
|-
| Horizon || ||
|-
| Glance || ||
|-
| Ceilometer || Chris Dent || cdent
|-
| Heat || Steve Baker || stevebaker
|-
| Oslo || Davanum Srinivas || dims
|-
| Trove || Nikhil Manchanda and Peter Stachowski || SlickNik and peterstac
|-
| Sahara || Luigi Toscano and Sergey Lukjanov || tosky and SergeyLukjanov
|-
| Ironic || Adam Gandelman || adam_g
|-
| Zaqar || ||
|-
| Barbican || Steve Heyman || hockeynut
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Joe Gordon or Michael Still || Jog0 or mikal
|-
| Cinder || Mike Perez || thingee
|-
| Swift || Atul Jha or Chuck Thier || koolhead or creight
|-
| Neutron || Edgar Magana || emagana
|-
| Keystone || Steve Martinelli || stevemar
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Heat || Randall Burt || randallburt
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Trove || Laurel Michaels, Matt Griffin || laurelm mattgriffin
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Ironic || Mitsuhiro SHIGEMATSU || pshige
|-
| Zaqar || ||
|-
| Barbican || Constanze Kratel || constanze
|-
| Murano || Ekaterina Chernova || katyafervent
|-
| Manila || ||
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Adam Gandelman || adam_g
|-
| Keystone || Dolph Mathews || dolphm
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kyle Mestery (Ihar Hrachyshka?) || mestery (ihrachyshka?)
|-
| Nova || ||
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Amrith Kumar || amrith
|-
|}

== Vulnerability management ==

The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Lin Hua Cheng || lhcheng
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Dolph Mathews || dolphm
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Michael Still || mikal
|-
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Nikhil Manchanda || SlickNik
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-api on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Erno Kuvaja || jokke_
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Nikolay Starodubtsev || Nikolay_St
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig
|-
| Documentation || Andreas Jaeger|| AJaeger
|}

== Product Working Group ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Manilla ||Pete Chadwick ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Horizon || Carol Barrett || barrett
|-
| Keystone || Sheena Gregson ||
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| Swift || Phil Willains || philipw
|-
| Glance || Nate Ziemann || nate_zman
|-
|OSClient || Megan Rossetti ||
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean M. Collins || sc68cal || Neutron liaison for Nova
|-
| || Brent Eagles || beagles || Nova liaison for Neutron
|-
| Nova / Glance || || ||
|-
| || Fei Long Wang || flwang || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova
|-
| || Michael Davies || mrda || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

Meetings/Horizon

2015-02-20T19:25:43Z

Doug Fish: /* Agenda for Feb 25 2000 UTC */

The [[OpenStack]] [[Horizon]] Team holds public meetings in #openstack-meeting-3 at alternating times.
* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=20&min=0&sec=0 2000 UTC]
* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=12&min=0&sec=0 1200 UTC]

Everyone is encouraged to attend.

Upcoming meeting schedule:
* Jan 7 1200 UTC
* Jan 14 2000 UTC
* Jan 21 1200 UTC
* Jan 28 2000 UTC
* Feb 4 1200 UTC
* Feb 11 2000 UTC

== Apologies for absence ==
* amotoki (Dec 3) -- Every 200UTC meeting

== Agenda for Feb 25 2000 UTC ==
* Use of discoverd in Tuskar-UI [rdopiera]?
* Review Blueprint: https://blueprints.launchpad.net/horizon/+spec/k2k-federation (doug-fish)

== Agenda for Feb 18 1200 UTC ==
* Use of discoverd in Tuskar-UI [rdopiera]

== Agenda for Feb 11 2000 UTC ==
* Angular work status
** policy and settings currently blocking
** virtual sprint proposal
*** https://wiki.openstack.org/wiki/VirtualSprints
* Summit planning
** session types/quantity -- http://lists.openstack.org/pipermail/openstack-dev/2015-January/054122.html
* Pre-Summit Meetup (TravT)

== Agenda for Feb 4 1200 UTC ==
* Switching to bower from xstatic https://blueprints.launchpad.net/horizon/+spec/static-file-bower (r1chardj0n3s)

== Agenda for Jan 28 2000 UTC ==
* Updating to Jasmine 2 https://blueprints.launchpad.net/horizon/+spec/update-jasmine (there are linked reviews) (mattfarina)
* JavaScript cleanup: reduce number of jQuery objects being created https://bugs.launchpad.net/horizon/+bug/1412971 (mattfarina)

== Agenda for Jan 7 1200 UTC ==
* Review blueprint https://blueprints.launchpad.net/horizon/+spec/serial-console (mzoeller, rbertram)
* Angular work blockers: Xstatic now or wait on Bower? need reviews! (tqtran)

== Agenda for Dec 17 2000 UTC ==
* packaging Thunderdome: xstatic vs bower; two packaging systems enter, one packaging system leaves
* REST API: should we be rewriting property names?
* REST API: Death by a million dependencies. Can we fasttrack the base decorator patch and then iterateː https://review.openstack.org/#/c/136676/40

== Agenda for Dec 10 1200 UTC ==
* Next step with 3rd party components & packaging (xstatic / bower)
* State of REST API - how much should be implemented?

== Agenda for Dec 3 2000 UTC ==
* Moved blueprint review list to https://wiki.openstack.org/wiki/Horizon/Blueprint_Reviews
* Repo split and names
* Next step with 3rd party components & packaging (xstatic / bower)
* State of REST API - how much should be implemented?
* New cinder rest API to get policy (https://review.openstack.org/#/c/136980/) - feedback please? (DuncanT)

== Agenda for next meeting (Nov 25) ==
* Close on new meeting times (david-lyle)
** (r1chardj0n3s) ran a doodle poll on the the ML
*** 20:00 UTC Wed
*** 12:00 UTC Mon, Wed, Thurs, Fri
* Some feedback from UX people is wanted regarding the patch https://review.openstack.org/#/c/113206/ What's the best default behavior for modal in Horizon: should it close when the User clicks outside of it or should not (tsufiev)? Another option is to use David Lyle's solution https://review.openstack.org/#/c/23037/3 (needs to be updated and cleaned)
* FYI: Integration tests on the gate (jpich)
** http://lists.openstack.org/pipermail/openstack-dev/2014-November/051490.html
=== Review Blueprints for Approval in Kilo ===
* https://blueprints.launchpad.net/horizon/+spec/launch-instance-floating-ip-allocation-association
* https://blueprints.launchpad.net/horizon/+spec/glance-metadata-definitions-base-admin-ui
* https://blueprints.launchpad.net/horizon/+spec/metadata-widget-multivalue-selection
* https://blueprints.launchpad.net/horizon/+spec/move-policy-engine
* https://blueprints.launchpad.net/horizon/+spec/domain-based-rbac
* https://blueprints.launchpad.net/horizon/+spec/identity-rbac -- OBSOLETE
* https://blueprints.launchpad.net/horizon/+spec/make-batchaction-help-text-configurable
* https://blueprints.launchpad.net/horizon/+spec/vol-type-extra-specs-describe
* https://blueprints.launchpad.net/horizon/+spec/vol-type-extra-specs-validate
* https://blueprints.launchpad.net/horizon/+spec/volume-bootable-flag
* https://blueprints.launchpad.net/horizon/+spec/volume-type-set-backend-name
* https://blueprints.launchpad.net/horizon/+spec/filtered-client-side-table

== Previous meetings ==
http://eavesdrop.openstack.org/meetings/horizon/

Meetings/Horizon

2015-02-20T19:25:23Z

Doug Fish: /* Agenda for Feb 25 2000 UTC */

The [[OpenStack]] [[Horizon]] Team holds public meetings in #openstack-meeting-3 at alternating times.
* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=20&min=0&sec=0 2000 UTC]
* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=12&min=0&sec=0 1200 UTC]

Everyone is encouraged to attend.

Upcoming meeting schedule:
* Jan 7 1200 UTC
* Jan 14 2000 UTC
* Jan 21 1200 UTC
* Jan 28 2000 UTC
* Feb 4 1200 UTC
* Feb 11 2000 UTC

== Apologies for absence ==
* amotoki (Dec 3) -- Every 200UTC meeting

== Agenda for Feb 25 2000 UTC ==
* Use of discoverd in Tuskar-UI [rdopiera]?
* Review Blueprint: https://blueprints.launchpad.net/horizon/+spec/k2k-federation

== Agenda for Feb 18 1200 UTC ==
* Use of discoverd in Tuskar-UI [rdopiera]

== Agenda for Feb 11 2000 UTC ==
* Angular work status
** policy and settings currently blocking
** virtual sprint proposal
*** https://wiki.openstack.org/wiki/VirtualSprints
* Summit planning
** session types/quantity -- http://lists.openstack.org/pipermail/openstack-dev/2015-January/054122.html
* Pre-Summit Meetup (TravT)

== Agenda for Feb 4 1200 UTC ==
* Switching to bower from xstatic https://blueprints.launchpad.net/horizon/+spec/static-file-bower (r1chardj0n3s)

== Agenda for Jan 28 2000 UTC ==
* Updating to Jasmine 2 https://blueprints.launchpad.net/horizon/+spec/update-jasmine (there are linked reviews) (mattfarina)
* JavaScript cleanup: reduce number of jQuery objects being created https://bugs.launchpad.net/horizon/+bug/1412971 (mattfarina)

== Agenda for Jan 7 1200 UTC ==
* Review blueprint https://blueprints.launchpad.net/horizon/+spec/serial-console (mzoeller, rbertram)
* Angular work blockers: Xstatic now or wait on Bower? need reviews! (tqtran)

== Agenda for Dec 17 2000 UTC ==
* packaging Thunderdome: xstatic vs bower; two packaging systems enter, one packaging system leaves
* REST API: should we be rewriting property names?
* REST API: Death by a million dependencies. Can we fasttrack the base decorator patch and then iterateː https://review.openstack.org/#/c/136676/40

== Agenda for Dec 10 1200 UTC ==
* Next step with 3rd party components & packaging (xstatic / bower)
* State of REST API - how much should be implemented?

== Agenda for Dec 3 2000 UTC ==
* Moved blueprint review list to https://wiki.openstack.org/wiki/Horizon/Blueprint_Reviews
* Repo split and names
* Next step with 3rd party components & packaging (xstatic / bower)
* State of REST API - how much should be implemented?
* New cinder rest API to get policy (https://review.openstack.org/#/c/136980/) - feedback please? (DuncanT)

== Agenda for next meeting (Nov 25) ==
* Close on new meeting times (david-lyle)
** (r1chardj0n3s) ran a doodle poll on the the ML
*** 20:00 UTC Wed
*** 12:00 UTC Mon, Wed, Thurs, Fri
* Some feedback from UX people is wanted regarding the patch https://review.openstack.org/#/c/113206/ What's the best default behavior for modal in Horizon: should it close when the User clicks outside of it or should not (tsufiev)? Another option is to use David Lyle's solution https://review.openstack.org/#/c/23037/3 (needs to be updated and cleaned)
* FYI: Integration tests on the gate (jpich)
** http://lists.openstack.org/pipermail/openstack-dev/2014-November/051490.html
=== Review Blueprints for Approval in Kilo ===
* https://blueprints.launchpad.net/horizon/+spec/launch-instance-floating-ip-allocation-association
* https://blueprints.launchpad.net/horizon/+spec/glance-metadata-definitions-base-admin-ui
* https://blueprints.launchpad.net/horizon/+spec/metadata-widget-multivalue-selection
* https://blueprints.launchpad.net/horizon/+spec/move-policy-engine
* https://blueprints.launchpad.net/horizon/+spec/domain-based-rbac
* https://blueprints.launchpad.net/horizon/+spec/identity-rbac -- OBSOLETE
* https://blueprints.launchpad.net/horizon/+spec/make-batchaction-help-text-configurable
* https://blueprints.launchpad.net/horizon/+spec/vol-type-extra-specs-describe
* https://blueprints.launchpad.net/horizon/+spec/vol-type-extra-specs-validate
* https://blueprints.launchpad.net/horizon/+spec/volume-bootable-flag
* https://blueprints.launchpad.net/horizon/+spec/volume-type-set-backend-name
* https://blueprints.launchpad.net/horizon/+spec/filtered-client-side-table

== Previous meetings ==
http://eavesdrop.openstack.org/meetings/horizon/

Horizon/BrowserSupport

2014-08-20T15:13:55Z

Doug Fish: /* Icehouse */

== Supported browsers ==

Horizon is primarily tested and supported on the latest version of Firefox, the latest version of Chrome, and IE9+. Issues related to Safari and Opera will also be considered.

This page aims to informally document what that means for different releases, everyone is warmly encouraged to update this page based on the versions they've tested with.

=== Juno ===

{| class="wikitable"
|-
! !! Status !! Notes
|-
| Firefox 31+ || Very good ||
|-
| Firefox || Very good || Versions?
|-
| Firefox ESR || ? ||
|-
| Chrome || Very good || Versions?
|-
| IE 11 || Good? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 10 || Good? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 9 || ? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 8 and below || Not supported. || No.
|-
| Safari || ? ||
|-
| Opera || ? ||
|}

'''Very good:''' Should work perfectly | '''Good:''' Should look nice and work fine, maybe a few visual hiccups | '''No:''' Not supported

=== Icehouse ===

{| class="wikitable"
|-
! !! Status !! Notes
|-
| Firefox || Very good || Versions?
|-
| Firefox ESR || Very good || Windows 24.7.0 ESR
|-
| Chrome || Very good || Windows Version 36
|-
| IE 11 || ? ||
|-
| IE 10 || ? ||
|-
| IE 9 || ? ||
|-
| IE 8 || ? ||
|-
| Safari || ? ||
|-
| Opera || ? ||
|}

Horizon/BrowserSupport

2014-08-20T15:11:46Z

Doug Fish: /* Icehouse */

== Supported browsers ==

Horizon is primarily tested and supported on the latest version of Firefox, the latest version of Chrome, and IE9+. Issues related to Safari and Opera will also be considered.

This page aims to informally document what that means for different releases, everyone is warmly encouraged to update this page based on the versions they've tested with.

=== Juno ===

{| class="wikitable"
|-
! !! Status !! Notes
|-
| Firefox 31+ || Very good ||
|-
| Firefox || Very good || Versions?
|-
| Firefox ESR || ? ||
|-
| Chrome || Very good || Versions?
|-
| IE 11 || Good? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 10 || Good? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 9 || ? || [https://bugs.launchpad.net/horizon/+bugs?field.tag=ie Open IE bugs]. Compatibility mode must be turned off
|-
| IE 8 and below || Not supported. || No.
|-
| Safari || ? ||
|-
| Opera || ? ||
|}

'''Very good:''' Should work perfectly | '''Good:''' Should look nice and work fine, maybe a few visual hiccups | '''No:''' Not supported

=== Icehouse ===

{| class="wikitable"
|-
! !! Status !! Notes
|-
| Firefox || Very good || Versions?
|-
| Firefox ESR || Very good || Windows 24.7.0 ESR
|-
| Chrome || Very good || Versions?
|-
| IE 11 || ? ||
|-
| IE 10 || ? ||
|-
| IE 9 || ? ||
|-
| IE 8 || ? ||
|-
| Safari || ? ||
|-
| Opera || ? ||
|}

Meetings/Horizon

2014-06-30T14:58:17Z

Doug Fish: /* Agenda for next meeting (June 24) */

Gerrit Workflow

2014-05-30T22:48:53Z

Doug Fish: Added note to not use the Change-Id, because that's bad.

= Gerrit Workflow Quick Reference =
Use this section as a quick reference for commands that you need to run to begin work in a new repository. Read this entire section before you complete the steps in the workflow for the first time. Then, review this section when you start work on a new [[OpenStack]] project. For a more complete description of the setup, see [[GerritJenkinsGit]].

[[File:code_review_static.png|link=:File:code_review.svg]]

== Account Setup ==
You'll need a [https://launchpad.net/+login Launchpad account], since this is how the Web interface for the Gerrit Code Review system will identify you. This is also useful for automatically crediting bug fixes to you when you address them with your code commits.

If you haven't already, [https://www.openstack.org/join/ join The OpenStack Foundation] (it's free and required for all code contributors). Among other privileges, this also allows you to vote in elections and run for elected positions within The OpenStack Project. When signing up for Foundation Membership, make sure to give the same E-mail address you'll use for code contributions, since this will need to match your preferred E-mail address in Gerrit.

Visit https://review.openstack.org/ and click the '''Sign In''' link at the top-right corner of the page. Log in with your Launchpad ID.

Because Gerrit uses Launchpad OpenID single sign-on, you won't need a separate password for Gerrit, and once you log in to one of Launchpad, Gerrit, or Jenkins, you won't have to enter your password for the others.

Unless you are an U.S. Government Employee (see below), [https://review.openstack.org/#/settings/agreements agree to the Individual Contributor License Agreement] and provide contact information. Your full name and E-mail address will be public (since they also appear in project commit logs) and the latter needs to match the user.email in your Git configuration. The other contact information (postal address, phone numbers) will be kept confidential and is only used as a fallback record in the unlikely event The OpenStack Foundation needs to reach you directly over code contribution related matters. This contact information can also be easily [https://review.openstack.org/#/settings/contact updated] later if desired, but make sure the primary E-mail address always matches the one you set for your OpenStack Foundation Membership--otherwise Gerrit will give you an error message and refuse to accept your contact information.

Employees of the the U.S. Government do not sign the Individual CLA. Instead, someone with authority to sign on behalf of your agency should sign the [[GovernmentCLA|U.S. Government Contributor License Agreement]]. Please contact the OpenStack Foundation to initiate this process.

If you are '''contributing on behalf of a company''' or organization, you still need to sign the ICLA above but someone at your company or organization also needs to sign the [https://review.openstack.org/#/settings/agreements Corporate Contributor License Agreement] providing a list of people authorized to commit code to OpenStack. Check [[HowToUpdateCorporateCLA|How to update the CCLA]] to provide changes to such list. A list of current companies and organizations with an existing [[Contributors/Corporate|Corporate CLA]] is available for your review.

You'll also want to [https://review.openstack.org/#/settings/ssh-keys upload an SSH key] while you're at it, so that you'll be able to [[GerritWorkflow#Committing_Changes|commit changes for review]] later.

Ensure that you have run these steps to let git know about your email address:

<pre><nowiki>
git config --global user.name "Firstname Lastname"
git config --global user.email "your_email@youremail.com"
</nowiki></pre>

To check your git configuration:

<pre><nowiki>
git config --list
</nowiki></pre>

== Git Review Installation ==
We recommend using the "git-review" tool which is a git subcommand that handles all the details of working with Gerrit, the code review system used in [[OpenStack]] development. Before you start work, make sure you have git-review installed on your system.

On Ubuntu, MacOSx, or most other Unix-like systems, it is as simple as:

<pre><nowiki>
pip install git-review
</nowiki></pre>

On Ubuntu Precise (12.04) and later, git-review is included in the distribution, so install it as any other package:

<pre><nowiki>
apt-get install git-review
</nowiki></pre>

On Fedora 16 and later, git-review is included into the distribution, so install it as any other package:

<pre><nowiki>
yum install git-review
</nowiki></pre>

On Fedora 15 and earlier you have to install pip (its package name is `python-pip`), then install git-review using pip in a conventional way.

On Red Hat Enterprise Linux, you must first enable the [http://fedoraproject.org/wiki/EPEL EPEL] repository, then install it as any other package:

<pre><nowiki>
yum install git-review
</nowiki></pre>

On openSUSE 12.2 and later, git-review is included in the distribution under the name python-git-review, so install it as any other package:
<pre><nowiki>
zypper in python-git-review
</nowiki></pre>

All of git-review's interactions with gerrit are sequences of normal git commands. If you want to know more about what it's doing, just add -v to the options and it will print out all of the commands it's running.

== SSH Setup ==

If you suffer from [https://github.com/net-ssh/net-ssh/issues/93 an incompetent middlebox in the network] between your machine and review.openstack.org then ''git review'' and ''git fetch'' will mysteriously fail with complaints about "Connection reset by peer". To work around this,
create/edit your .ssh/config to reduce the size of your client's Key Exchange Init message; one simple way to do it is to configure the set of MAC algorithms to just one, hmac-md5. When doing a ''git fetch'' use an SSH URL rather than an HTTPS one, because your ~/.ssh/config will be consulted in the SSH case but not the HTTPS case.

== Project Setup ==

=== For Unit Tests Only or With Indirect Integration Testing ===

''This method is suitable for repos on your laptop and supports running unit tests. It also supports both unit testing and [[Testing#Indirect_Approach|indirect integration testing]].''

Clone a project in the usual way, for example:

<pre><nowiki>
git clone git://git.openstack.org/openstack/nova.git
</nowiki></pre>

You may want to ask git-review to configure your project to know about Gerrit at this point. If you don't, it will do so the first time you submit a change for review, but you probably want to do this ahead of time so the Gerrit Change-Id commit hook gets installed. To do so (again, using Nova as an example):

<pre><nowiki>
cd nova
git review -s
</nowiki></pre>

Git-review checks that you can log in to gerrit with your ssh key. It assumes that your gerrit/launchpad user name is the same as the current running user. If that doesn't work, it asks for your gerrit/launchpad user name. You can avoid that question by configuring your Gerrit username, as follows.

<pre><nowiki>
git config --global gitreview.username yourgerritusername
</nowiki></pre>

If you don't remember your Gerrit user name go to the [https://review.openstack.org/#/settings/ settings page on gerrit] to check it out (it's not your email address).

Note that you can verify the SSH host keys for review.openstack.org here: https://review.openstack.org/#/settings/ssh-keys

If you get the error "We don't know where your gerrit is.", you will need to add a new git remote. The url should be in the error message. Copy that and create the new remote.

<pre><nowiki>
git remote add gerrit ssh://<username>@review.openstack.org:29418/openstack/nova.git
</nowiki></pre>

In the project directory, you have a `.git` hidden directory and a `.gitreview` hidden file. You can see them with:

<pre><nowiki>
ls -la
</nowiki></pre>

=== For System Tests ===

''This method is suitable for running system-level and integration tests with some or all of OpenStack services.''

Use [[DevStack]] to fetch, configure, and run the set of projects you want in your system. DevStack takes control of the system where it runs and we highly suggest to use it only in disposable virtual machines. It will check out each project repo to the destination defined in your <code>local.conf</code> config file (the default is <code>/opt/stack</code>). You can do the git review setup as above to work in DevStack's repos, but note that DevStack is rather territorial about the repos it checks out and uncommitted changes can be lost when running <code>stack.sh</code>. This is not the recommended way to do more than minor work on projects.

Also note that by default DevStack does not assure installation of the prerequisites for running unit tests. To do that set <code> INSTALL_TESTONLY_PACKAGES=True</code> in <code>local.conf</code>.

== Normal Workflow ==
Once your local repository is set up as above, you must use the following workflow.

Make sure you have the latest upstream changes:

<pre><nowiki>
git remote update
git checkout master
git pull --ff-only origin master
</nowiki></pre>

Create a [http://git-scm.com/book/en/Git-Branching-Branching-Workflows#Topic-Branches topic branch] to hold your work and switch to it. If you are working on a blueprint, name your topic branch '''bp/BLUEPRINT''' where BLUEPRINT is the name of a blueprint in launchpad (for example, "bp/authentication"). The general convention when working on bugs is to name the branch '''bug/BUG-NUMBER''' (for example, "bug/1234567"). Otherwise, give it a meaningful name because it will show up as the topic for your change in Gerrit.

<pre><nowiki>
git checkout -b TOPIC-BRANCH
</nowiki></pre>

To generate documentation artifacts, navigate to the directory where the pom.xml file is located for the project and run the following command:

<pre><nowiki>
mvn clean generate-sources
</nowiki></pre>

For complete information about generating documentation artifacts, see "Build Output Locally" on the https://wiki.openstack.org/wiki/Documentation/HowTo page.

=== Running Unit Tests ===

See [[Testing#Unit_Tests|Unit Tests in the Testing page]].

=== Running System Tests ===

See [[Testing#IntegrationTests|IntegrationTests on the Testing page]].

=== Committing Changes ===
Prior to checking in make sure that you [[Testing#Unit_Tests|run the unit tests]].

[[GitCommitMessages|Git commit messages]] should start with a short 50 character or less summary in a single paragraph. The following paragraph(s) should explain the change in more detail.

If your changes addresses a blueprint or a bug, be sure to mention them in the commit message using the following syntax:

<pre><nowiki>
Implements: blueprint BLUEPRINT
Closes-Bug: ####### (Partial-Bug or Related-Bug are options)
</nowiki></pre>

For example:

<pre><nowiki>
Adds keystone support

...Long multiline description of the change...

Implements: blueprint authentication
Closes-Bug: #123456
Change-Id: I4946a16d27f712ae2adf8441ce78e6c0bb0bb657
</nowiki></pre>

Note that in most cases the Change-Id line should be automatically added by a Gerrit commit hook that you will want to install. See [[Gerrit_Workflow#Project_Setup|Project Setup]] for details on configuring your project for Gerrit. If you already made the commit and the Change-Id was not added, do the Gerrit setup step and run:
<pre>git commit --amend</pre>
The commit hook will automatically add the Change-Id when you finish amending the commit message, even if you don't actually make any changes.

Make your changes, commit them, and submit them for review:
<pre><nowiki>
git commit -a
git review
</nowiki></pre>

'''Caution: Do not check in changes on your master branch. Doing so will cause merge commits when you pull new upstream changes, and merge commits will not be accepted by Gerrit.

=== Review ===
Once the code is committed, it appears at https://review.openstack.org. Please refer http://wiki.openstack.org/GerritJenkinsGit for more information. If the link corresponding to your code is clicked, it shows the status and other information. Automatic testing occurs and the results are displayed. Reviewers comment in the comment box or in the code itself.

If someone leaves an in-line comment, you can see it from expanded "Patch Set." "Comments" column shows how many comments are in each file. If you click a file name that has comments, the new page shows a diff page with the reviewer's name and comments. Click "Reply" and write your response. It is saved as a draft if you click "Save." Now, go back to the page that shows a list of patch sets and click "Review," and then, click "Publish comments."

If your code is not ready for review, click "Work in Progress" to indicate that a reviewer does not need to review it for now. Note that the button is invisible until you login the site.

More on what happens next is described on [[GerritJenkinsGit#Reviewing_a_Change]].

=== Work in Progress ===

A change can be marked Work in Progress if, for example, it is not ready for merging, or even general code review, but you would still like to get early comments. Marking a change work in progress is simple, leave a comment on your patch setting "Workflow" to -1. Changes in this state are public and can be viewed by everyone. Authenticated users can leave comments as they would in normal code review, but changes in this state cannot be submitted for merging. This allows you to solicit early feedback without worry that incomplete changes will be accidentally merged.

<pre><nowiki>
git commit -a
git review
# Go to change in Gerrit web UI and leave a comment with Workflow set to -1.
</nowiki></pre>

'''Caution: The Draft feature in Gerrit may be tempting, but it is not friendly to the CI systems and should not be used. Use the Work in Progress feature instead.'''

=== Long-lived Topic Branches ===
If you are working on a larger project, you may be working on your topic branch for a while. In that case, you may want to check in your changes frequently during development and you must rebase your change to the current state of the master repository before submitting it for code review. In these situations you should prepare your change carefully before submitting it.

If the master repository has changed since you started, you should rebase your changes to the current state. And if you have made many small commits, you should squash them so that they do not show up in the public repository. Remember: each commit becomes a change in Gerrit, and must be approved separately. If you are making one "change" to the project, squash your many "checkpoint" commits into one commit for public consumption. Here's how:

<pre><nowiki>
git checkout master
git pull origin master
git checkout TOPIC-BRANCH
git rebase -i master
</nowiki></pre>

Use the editor to squash any commits that should not appear in the public history. If you want one change to be submitted to Gerrit, you should only have one "pick" line at the end of this process. After completing this, you can prepare your public commit message(s) in your editor. You start with the commit message from the commit that you picked, and it should have a Change-Id line in the message. Be sure to leave that Change-Id line in place when editing.

Once the commit history in your branch looks correct, run '''git review''' to submit your changes to Gerrit.

=== Updating a Change ===
If the code review process suggests additional changes, make and amend the changes to the the existing commit. Leave the existing Change-Id: footer in the commit message as-is. Gerrit knows that this is an updated patch for an existing change:

<pre><nowiki>
git commit -a --amend
git review
</nowiki></pre>

=== Add dependency ===
When you want to start new work that is based on the commit under the review, you can add the commit as a dependency.

<pre><nowiki>
#fetch change under review and check out branch based on that change.
git review -d $PARENT_CHANGE_NUMBER
git checkout -b $DEV_TOPIC_BRANCH
# Edit files, add files to git
git commit
git review
</nowiki></pre>

* '''NOTE:''' git review rebases the existing change (the dependency) and the new commit if there is a conflict against the branch they are being proposed to. Typically this is desired behavior as merging cannot happen until these conflicts are resolved. If you don't want to deal with new patchsets in the existing change immediately you can pass the -R option to git review in the last step above to prevent rebasing. This requires future rebasing to resolve conflicts.

* '''NOTE:''' $PARENT_CHANGE_NUMBER is NOT the Change-Id: value! It is the last section of the gerrit URL. It should be a 5 or 6 digit number.

If the commit your work depends on is updated, and you need to get the latest patch from the depended commit, you can do the following.

<pre><nowiki>
# fetch and checkout the parent change
git review -d $PARENT_CHANGE_NUMBER
# Note the branch created by git review. Should be review/$USER/$PARENT_CHANGE_ID or similar.
# Checkout existing development topic branch for the child commit.
git checkout $DEV_TOPIC_BRANCH
# Rebase onto updated parent branch to create a dependency on the latest version of that change.
git rebase -i review/$USER/$PARENT_CHANGE #This is the branch created by git review that was noted earlier.
# Do the revisions
git commit -a --amend
# submit for review
git review
</nowiki></pre>

The note for the previous example applies here as well. Typically you want the rebase behavior in git review. If you would rather postpone resolving merge conflicts you can use git review -R as the last step above.

Design Summit/Juno/Etherpads

2014-05-09T21:28:26Z

Doug Fish: /* Horizon */

[[Category:Summit]]
[[Category:Juno]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== Ceilometer ==

* Wed 0900-0940 [https://etherpad.openstack.org/p/ceilometer-agent-repartition Ceilometer agents repartition]
* Wed 0950-1030 Improve Ceilometer test strategy
* Wed 1100-1140 Complex query on Ceilometer stats & project-specific meters
* Wed 1150-1230 [https://etherpad.openstack.org/p/ceilometer-tsdaas Rethinking Ceilometer as Time-Series-Data-as-a-Service]
* Wed 1350-1430 [https://etherpad.openstack.org/p/ceilometer-schema Revise Ceilometer data model to improve performance]
* Wed 1440-1520 Ceilometer Dev/Ops Session
* Wed 1530-1610 [https://etherpad.openstack.org/p/ceilometer-snmp-inspector Ceilometer SNMP improvements & code-free meters]
* Wed 1630-1710 [https://etherpad.openstack.org/p/ceilometer-alarm-and-log-improvments Ceilometer alarm evaluation improvements & effective logging]
* Wed 1720-1800 Ironic and Ceilometer
* Thurs 0900-0940 [https://etherpad.openstack.org/p/juno-summit-metering-network-services Deploying Ceilometer w/ TripleO & Metering Network Services]

== Cinder ==

* Thurs 15.30-16:10 [https://etherpad.openstack.org/p/juno-cinder-backup-restore Volume Backup\Restore]
* Thurs 16:10-16:50 [https://etherpad.openstack.org/p/juno-cinder-volume-replication Volume Replication]
* Thurs 17:00-17:40 [https://etherpad.openstack.org/p/juno-cinder-DRBD DRBD For Cinder-Volumes]
* Friday 09:00-09:40 [https://etherpad.openstack.org/p/juno-cinder-nfs-in-cinder NFS and its role within Cinder]
* Friday 10:00-10:40 [https://etherpad.openstack.org/p/juno-cinder-cinder-consistency-groups Adding Consistency Groups to Cinder]
* Friday 10:50-11:30 [https://etherpad.openstack.org/p/juno-cinder-3rd-party-cert-and-verification 3'rd party certificiation and CI systems]
* Friday 11:40-12:20 [https://etherpad.openstack.org/p/juno-cinder-changed-block-list Changed Block List for Cinder Volumes]
* Friday 13:20-14:00 [https://etherpad.openstack.org/p/juno-cinder-state-and-workflow-management Cinder State and Workflow Management]
* Friday 14:10-14:50 [https://etherpad.openstack.org/p/juno-cinder-framework-for-state-reporting Framework for detailed Volume Stats reporting]
* Friday 15:00-15:40 [https://etherpad.openstack.org/p/juno-cinder-multiple-pools-per-backend Mulitple Pools per Cinder Backend]
* Friday 16:00-16:40 [https://etherpad.openstack.org/p/juno-cinder-whats-a-cinder-driver What is a Cinder Driver]

==Cross-Project==
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/juno-cross-project-future-of-python The Future of Python Support]
* Tues 11:15-12:45 [https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis Consistency Across OpenStack REST APIs]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-cross-oslo-library-releases New Oslo Library Releases and Your Project]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-dealing-rejections Dealing with changes of plans, rejections and more]
* Tues 14:50-16:20 [https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]
* Tues 15:40-16:20 [https://etherpad.openstack.org/p/juno-cross-project-quota-management-endpoint Cross-project Quota Management Service Endpoint]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-cross-project-tracking-features Tracking incoming features]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-gate How do we make it easier to fix the Gate?]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-openstackclient Clients and SDKs Part I]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-test-maxtrices Test Matrices and Feature Parity]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-summit-sdk Clients and SDKs Part II]

== Devstack ==
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]

== Documentation ==

* Wed 09:00 [https://etherpad.openstack.org/p/installation-guide-audit Installation Guide Discussion]
* Thu 09:50 [https://etherpad.openstack.org/p/summit0514-session-patching-the-docs-process Patching the Documentation Process]

== Glance ==
* Wed 5:20-6:00: [https://etherpad.openstack.org/p/juno-hot-artifacts-repository-finalize-design Hot/Artifacts repository finalize design]
* Thur 9:00-9:40: [https://etherpad.openstack.org/p/juno-glance-store-and-future-features Glance Store and Future Features]
* Thur 9:50-10:30: [https://etherpad.openstack.org/p/juno-tasks-review-and-taskflow Task Review and Taskflow]
* Thur 11:00-11:40: [https://etherpad.openstack.org/p/juno-adding-functional-operations-to-glance-api Adding functional operations to Glance API]
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-poking-image-filesystem Poking Image Filesystem]

== Heat ==

* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]

== Horizon ==
* Wed 15:30-16:10 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]
* Wed 17:20-18:00 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]
* Thu 17:00-17:40 [https://etherpad.openstack.org/p/juno-summit-horizon-tuskar-ui Tuskar-UI and its relationship to Horizon]
* Fri 09:00-09:40 [https://etherpad.openstack.org/p/juno-summit-horizon-usability-test-results Review Horizon Usability Test feedback, proposals]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-overview-page-horizon Better Overview Pages]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/Dashboard_Accessibility Dashboard Accessibility]
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]

== Infrastructure ==
* Wed 9:50 - [https://etherpad.openstack.org/p/juno-summit-elastic-recheck Elastic Recheck next steps]
* Wed 11:00 - [https://etherpad.openstack.org/p/juno-summit-jenkins-moving-forward Jenkins moving forward]
* Wed 11:50 - [https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing Improving Third Party Testing]
* Thu 11:00 - [https://etherpad.openstack.org/p/juno-infra-design-Vinz-review-system Discussion/design talk of Vinz code review system]
* Thu 11:50 - [https://etherpad.openstack.org/p/juno-infra-storyboard StoryBoard: current status & Juno plans]
* Fri 9:50 - [https://etherpad.openstack.org/p/juno-openid Replace Launchpad OpenID authentication]
* Fri 10:50 - [https://etherpad.openstack.org/p/translation-platform-discussion Translation platform discussion]

== Ironic ==

* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]

== Keystone ==

* Wed 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-hierarchical-multitenancy Hierarchical Multitenancy]
* Wed 13:50-14:30 [https://etherpad.openstack.org/p/juno-keystone-devops DevOps]
* Wed 14:40-15:20 [https://etherpad.openstack.org/p/juno-keystone-client python-keystoneclient]
* Thurs 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-authorization Authorization]
* Thurs 13:30-14:10 [https://etherpad.openstack.org/p/juno-keystone-federation Federation]
* Thurs 14:20-15:00 [https://etherpad.openstack.org/p/juno-keystone-locally-managed-identities Locally-managed identities]
* Fri 11:40-12:20 [https://etherpad.openstack.org/p/juno-keystone-user-ids User & Group IDs]
* Fri 13:20-14:00 [https://etherpad.openstack.org/p/juno-keystone-service-catalog Service Catalog]

== Marconi ==

* Tues 14:50 - [https://etherpad.openstack.org/p/juno-marconi-queue-flavors Queue Flavors]
* Tues 15:40 - [https://etherpad.openstack.org/p/juno-marconi-notifications-on-marconi Notifications on Marconi]
* Tues 16:40 - [https://etherpad.openstack.org/p/ATL-marconi-ops Marconi Dev/Ops Session]
* Tues 17:30 - [https://etherpad.openstack.org/p/juno-marconi-scale-single-queue Scaling an Individual Queue]

== Neutron ==
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]
* Wed 9:50-10:30: Code Review Process Improvements
* Wed 11:00-11:40: [https://etherpad.openstack.org/p/neutron-ipv6-atlanta-summit IPv6 status in Neutron]
* Wed 11:50-12:30: [https://etherpad.openstack.org/p/ML2_Juno_Roadmap ML2 Juno Roadmap] and [https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]
* Wed 13:50-14:30: Refactoring the Neutron Server Core
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]
* Wed 15:30-14:10: Integrating Tasks into Neutron
* Wed 16:30-17:10: [https://etherpad.openstack.org/p/juno-advanced-services Advanced Services] and [https://etherpad.openstack.org/p/juno-virtual-resource-for-service-chaining Virtual Resource for Service Chaining]
* Wed 17:20-18:00: [https://etherpad.openstack.org/p/Distributed-Virtual-Router Neutron Distributed Virtual Router Progress Update]
* Thu 9:00-9:40: [https://etherpad.openstack.org/p/TempestAndNeutronJuno Neutron QA and Testing]
* Thu 9:50-10:30: Sharing the load of operational responsibility
* Thu 11:00-11:40: Neutron LBaaS Update
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent Modular Layer2 Agents]
* Fri 10:50-11:30: [https://etherpad.openstack.org/p/group-based-policy Neutron Group Based Policy]
* Fri 11:40-12:30: [https://etherpad.openstack.org/p/juno-fwaas FWaaS] and [https://etherpad.openstack.org/p/juno-vpnaas VPNaaS]
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios
* Fri 14:10-14:50: [https://etherpad.openstack.org/p/hierarchical_network_topology Hierarchical Network Topologies]
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]
* Fri 16:00-16:40: Dynamic routing and [https://etherpad.openstack.org/p/juno-neutron-pluggable-external-network pluggable external networks]
* Fri 16:50-17:30: [https://etherpad.openstack.org/p/servicevm Service VM Discussion]

== Nova ==

'''Wednesday, May 14'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-third-party-ci Continuation of third party CI]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support Clustered hypervisor support in Nova]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-deprecating-baremetal The road to deprecating nova.virt.baremetal]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-data-transfer-service Data transfer service plug-in]
* 1:50pm [https://etherpad.openstack.org/p/juno-nova-live-upgrade Next steps in live upgrade]
* 2:40pm [https://etherpad.openstack.org/p/juno-nova-image-precaching Image precaching service]
* 3:30pm [https://etherpad.openstack.org/p/juno-nova-flavor-storage-revamp Flavor storage re-vamp]
* 4:30pm [https://etherpad.openstack.org/p/juno-nova-cross-project-interactions Rethinking cross project interactions]
* 5:20pm [https://etherpad.openstack.org/p/juno-nova-v2-on-v3-api-poc Nova V2 on V3 API implementation POC]

'''Thursday, May 15'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-hypev-new-features Hyper-V Driver new features]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-libvirt-driver-roadmap Libvirt driver roadmap for Juno]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-kvm-live-migration Improve performance of live migration on KVM]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-conductor-api limited conductor API]
* 1:30pm [https://etherpad.openstack.org/p/juno-nova-quota-state-management Implementing state management for quotas]
* 2:20pm [https://etherpad.openstack.org/p/juno-nova-multi-volume-snapshots Multi-Volume Snapshots]
* 3:10pm [https://etherpad.openstack.org/p/juno-nova-hypervisor-power-mgmt Hypervisor power management]
* 4:10pm [https://etherpad.openstack.org/p/juno-nova-sriov-support SR-IOV support]
* 5:00pm [https://etherpad.openstack.org/p/juno-nova-v3-api Nova V3 API]

'''Friday, May 16'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-vmware-driver-roadmap Vmwareapi driver roadmap for Juno]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-docker-driver-features Docker driver - features & testing]
* 10:50am [https://etherpad.openstack.org/p/juno-nova-gantt-apis Future of Gantt APIs and interfaces]
* 11:40am [https://etherpad.openstack.org/p/juno-nova-no-db-scheduler Common no DB Scheduler]
* 1:20pm [https://etherpad.openstack.org/p/juno-nova-scheduling-server-groups Simultaneous Scheduling for Server Groups]
* 2:10pm [https://etherpad.openstack.org/p/juno-nova-scheduler-hints-vm-lifecycle Scheduler hints for VM life cycle]
* 3:00pm [https://etherpad.openstack.org/p/juno-nova-devops Nova Dev/Ops Session]
* 4:00pm [https://etherpad.openstack.org/p/juno-nova-unsession Unsession]

== Ops ==
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]

* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]
* Fri 4:00 – 4:40 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]
* Fri 4:50 – 5:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]

== Oslo ==
* Wed 9:00 - 9:40 [https://etherpad.openstack.org/p/juno-oslo-release-plan Release Plan for Low-level Libraries]
* Wed 9:50 - 10:30 oslo.messaging status and plans for Juno
* Wed 11:00 - 11:40 [https://etherpad.openstack.org/p/olso.messaging_amqp_1.0 AMQP 1.0 protocol driver]
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session
* Thu 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-infra-library-testing Testing pre-releases of Oslo libs with apps]
* Thu 11:00 - 11:40 [https://etherpad.openstack.org/p/juno-osprofiler OpenStack cross service/project OpenStack profiler]
* Thu 15:10 - 16:00 [https://etherpad.openstack.org/p/juno-oslo-bayer Upstream chat with Mike Bayer]
* Thu 16:10 - 17:00 [https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy rpc proxy(oslo.messaging)]
* Fri 14:10 - 15:50 [https://etherpad.openstack.org/p/juno-summit-oslo-rootwrap oslo.rootwrap: performance and other improvements]
* Fri 15:00 - 16:40 Semantic versioning and oslo
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-pki-for-messaging PKI for messaging]

== QA ==

'''Wednesday'''
* 2:40 – 3:20 [https://etherpad.openstack.org/p/juno-summit-branchless-tempest Branchless Tempest]
* 3:30 – 4:10 [https://etherpad.openstack.org/p/juno-summit-tempest-documentation Tempest Documentation Gaps]
* 4:30 – 5:10 Functional API Testing - post dev QA vs TDD
* 5:20 – 6:00 [https://etherpad.openstack.org/p/juno-rally-and-tempest Rally and Tempest Integration]

'''Thursday'''
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]
* 2:20 – 3:00 [https://etherpad.openstack.org/p/juno-summit-negative-fuzzy-testing Negative Testing: Fuzzy Test Framework]
* 3:10 – 3:50 [https://etherpad.openstack.org/p/juno-summit-improve-ux-tools How to improve the UX of our Testing Tools]
* 4:10 – 4:50 [https://etherpad.openstack.org/p/juno-summit-tempest-gui-client-server Tempest, GUI, Client, Server]

'''Friday'''
* 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-grenade Grenade Current Status and Next Steps]
* 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]

== Release Management ==

* Wednesday 1:50pm [https://etherpad.openstack.org/p/juno-summit-release-branches Release branches, QA and requirements]
* Thursday 9:00am [https://etherpad.openstack.org/p/juno-summit-vmt Vulnerability management in Juno]
* Thursday 5:00pm [https://etherpad.openstack.org/p/StableIcehouse Stable branches maintenance]
* Friday 3:00pm [https://etherpad.openstack.org/p/juno-summit-release-schedule Juno release schedule and processes]
* Friday 4:50pm [https://etherpad.openstack.org/p/juno-summit-feedback Design Summit feedback]

== Sahara (ex. Savanna) ==

* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]

== Swift ==
== TripleO (Deployment) ==
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]
* Fri 13:20 - 14:00 [https://etherpad.openstack.org/p/juno-summit-tripleo-environment TripleO Development and Testing Environment]
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]

== Trove ==
== User Committee ==
== Other Projects ==
* [http://junodesignsummit.sched.org/event/6f9fe2ec2e6d3843139663a350cdc511 Tue 17:30 - 18:10] [https://etherpad.openstack.org/p/juno-summit-discovery-and-diagnostic-for-openstack Discovery and Diagnostic for OpenStack]
* [http://junodesignsummit.sched.org/event/ab6d8eed3c6fd85dc450c099aba22e11 Tue 12:05 - 12:45] [https://etherpad.openstack.org/p/juno-design-summit-designate-session-1 Designate Session 1]

Design Summit/Juno/Etherpads

2014-05-09T21:27:47Z

Doug Fish: /* Horizon */

[[Category:Summit]]
[[Category:Juno]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== Ceilometer ==

* Wed 0900-0940 [https://etherpad.openstack.org/p/ceilometer-agent-repartition Ceilometer agents repartition]
* Wed 0950-1030 Improve Ceilometer test strategy
* Wed 1100-1140 Complex query on Ceilometer stats & project-specific meters
* Wed 1150-1230 [https://etherpad.openstack.org/p/ceilometer-tsdaas Rethinking Ceilometer as Time-Series-Data-as-a-Service]
* Wed 1350-1430 [https://etherpad.openstack.org/p/ceilometer-schema Revise Ceilometer data model to improve performance]
* Wed 1440-1520 Ceilometer Dev/Ops Session
* Wed 1530-1610 [https://etherpad.openstack.org/p/ceilometer-snmp-inspector Ceilometer SNMP improvements & code-free meters]
* Wed 1630-1710 [https://etherpad.openstack.org/p/ceilometer-alarm-and-log-improvments Ceilometer alarm evaluation improvements & effective logging]
* Wed 1720-1800 Ironic and Ceilometer
* Thurs 0900-0940 [https://etherpad.openstack.org/p/juno-summit-metering-network-services Deploying Ceilometer w/ TripleO & Metering Network Services]

== Cinder ==

* Thurs 15.30-16:10 [https://etherpad.openstack.org/p/juno-cinder-backup-restore Volume Backup\Restore]
* Thurs 16:10-16:50 [https://etherpad.openstack.org/p/juno-cinder-volume-replication Volume Replication]
* Thurs 17:00-17:40 [https://etherpad.openstack.org/p/juno-cinder-DRBD DRBD For Cinder-Volumes]
* Friday 09:00-09:40 [https://etherpad.openstack.org/p/juno-cinder-nfs-in-cinder NFS and its role within Cinder]
* Friday 10:00-10:40 [https://etherpad.openstack.org/p/juno-cinder-cinder-consistency-groups Adding Consistency Groups to Cinder]
* Friday 10:50-11:30 [https://etherpad.openstack.org/p/juno-cinder-3rd-party-cert-and-verification 3'rd party certificiation and CI systems]
* Friday 11:40-12:20 [https://etherpad.openstack.org/p/juno-cinder-changed-block-list Changed Block List for Cinder Volumes]
* Friday 13:20-14:00 [https://etherpad.openstack.org/p/juno-cinder-state-and-workflow-management Cinder State and Workflow Management]
* Friday 14:10-14:50 [https://etherpad.openstack.org/p/juno-cinder-framework-for-state-reporting Framework for detailed Volume Stats reporting]
* Friday 15:00-15:40 [https://etherpad.openstack.org/p/juno-cinder-multiple-pools-per-backend Mulitple Pools per Cinder Backend]
* Friday 16:00-16:40 [https://etherpad.openstack.org/p/juno-cinder-whats-a-cinder-driver What is a Cinder Driver]

==Cross-Project==
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/juno-cross-project-future-of-python The Future of Python Support]
* Tues 11:15-12:45 [https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis Consistency Across OpenStack REST APIs]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-cross-oslo-library-releases New Oslo Library Releases and Your Project]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-dealing-rejections Dealing with changes of plans, rejections and more]
* Tues 14:50-16:20 [https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]
* Tues 15:40-16:20 [https://etherpad.openstack.org/p/juno-cross-project-quota-management-endpoint Cross-project Quota Management Service Endpoint]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-cross-project-tracking-features Tracking incoming features]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-gate How do we make it easier to fix the Gate?]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-openstackclient Clients and SDKs Part I]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-test-maxtrices Test Matrices and Feature Parity]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-summit-sdk Clients and SDKs Part II]

== Devstack ==
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]

== Documentation ==

* Wed 09:00 [https://etherpad.openstack.org/p/installation-guide-audit Installation Guide Discussion]
* Thu 09:50 [https://etherpad.openstack.org/p/summit0514-session-patching-the-docs-process Patching the Documentation Process]

== Glance ==
* Wed 5:20-6:00: [https://etherpad.openstack.org/p/juno-hot-artifacts-repository-finalize-design Hot/Artifacts repository finalize design]
* Thur 9:00-9:40: [https://etherpad.openstack.org/p/juno-glance-store-and-future-features Glance Store and Future Features]
* Thur 9:50-10:30: [https://etherpad.openstack.org/p/juno-tasks-review-and-taskflow Task Review and Taskflow]
* Thur 11:00-11:40: [https://etherpad.openstack.org/p/juno-adding-functional-operations-to-glance-api Adding functional operations to Glance API]
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-poking-image-filesystem Poking Image Filesystem]

== Heat ==

* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]

== Horizon ==
* Wed 15:30-16:10 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]
* Wed 17:20-18:00 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]
* Thu 17:00-17:40 [https://etherpad.openstack.org/p/juno-summit-horizon-tuskar-ui Tuskar-UI and its relationship to Horizon]
* Fri 09:00-09:40 [https://etherpad.openstack.org/p/juno-summit-horizon-usability-test-results Review Horizon Usability Test feedback, proposals]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-overview-page-horizon Better Overview Pages]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/Dashboard_Accessibility]
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]

== Infrastructure ==
* Wed 9:50 - [https://etherpad.openstack.org/p/juno-summit-elastic-recheck Elastic Recheck next steps]
* Wed 11:00 - [https://etherpad.openstack.org/p/juno-summit-jenkins-moving-forward Jenkins moving forward]
* Wed 11:50 - [https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing Improving Third Party Testing]
* Thu 11:00 - [https://etherpad.openstack.org/p/juno-infra-design-Vinz-review-system Discussion/design talk of Vinz code review system]
* Thu 11:50 - [https://etherpad.openstack.org/p/juno-infra-storyboard StoryBoard: current status & Juno plans]
* Fri 9:50 - [https://etherpad.openstack.org/p/juno-openid Replace Launchpad OpenID authentication]
* Fri 10:50 - [https://etherpad.openstack.org/p/translation-platform-discussion Translation platform discussion]

== Ironic ==

* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]

== Keystone ==

* Wed 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-hierarchical-multitenancy Hierarchical Multitenancy]
* Wed 13:50-14:30 [https://etherpad.openstack.org/p/juno-keystone-devops DevOps]
* Wed 14:40-15:20 [https://etherpad.openstack.org/p/juno-keystone-client python-keystoneclient]
* Thurs 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-authorization Authorization]
* Thurs 13:30-14:10 [https://etherpad.openstack.org/p/juno-keystone-federation Federation]
* Thurs 14:20-15:00 [https://etherpad.openstack.org/p/juno-keystone-locally-managed-identities Locally-managed identities]
* Fri 11:40-12:20 [https://etherpad.openstack.org/p/juno-keystone-user-ids User & Group IDs]
* Fri 13:20-14:00 [https://etherpad.openstack.org/p/juno-keystone-service-catalog Service Catalog]

== Marconi ==

* Tues 14:50 - [https://etherpad.openstack.org/p/juno-marconi-queue-flavors Queue Flavors]
* Tues 15:40 - [https://etherpad.openstack.org/p/juno-marconi-notifications-on-marconi Notifications on Marconi]
* Tues 16:40 - [https://etherpad.openstack.org/p/ATL-marconi-ops Marconi Dev/Ops Session]
* Tues 17:30 - [https://etherpad.openstack.org/p/juno-marconi-scale-single-queue Scaling an Individual Queue]

== Neutron ==
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]
* Wed 9:50-10:30: Code Review Process Improvements
* Wed 11:00-11:40: [https://etherpad.openstack.org/p/neutron-ipv6-atlanta-summit IPv6 status in Neutron]
* Wed 11:50-12:30: [https://etherpad.openstack.org/p/ML2_Juno_Roadmap ML2 Juno Roadmap] and [https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]
* Wed 13:50-14:30: Refactoring the Neutron Server Core
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]
* Wed 15:30-14:10: Integrating Tasks into Neutron
* Wed 16:30-17:10: [https://etherpad.openstack.org/p/juno-advanced-services Advanced Services] and [https://etherpad.openstack.org/p/juno-virtual-resource-for-service-chaining Virtual Resource for Service Chaining]
* Wed 17:20-18:00: [https://etherpad.openstack.org/p/Distributed-Virtual-Router Neutron Distributed Virtual Router Progress Update]
* Thu 9:00-9:40: [https://etherpad.openstack.org/p/TempestAndNeutronJuno Neutron QA and Testing]
* Thu 9:50-10:30: Sharing the load of operational responsibility
* Thu 11:00-11:40: Neutron LBaaS Update
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent Modular Layer2 Agents]
* Fri 10:50-11:30: [https://etherpad.openstack.org/p/group-based-policy Neutron Group Based Policy]
* Fri 11:40-12:30: [https://etherpad.openstack.org/p/juno-fwaas FWaaS] and [https://etherpad.openstack.org/p/juno-vpnaas VPNaaS]
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios
* Fri 14:10-14:50: [https://etherpad.openstack.org/p/hierarchical_network_topology Hierarchical Network Topologies]
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]
* Fri 16:00-16:40: Dynamic routing and [https://etherpad.openstack.org/p/juno-neutron-pluggable-external-network pluggable external networks]
* Fri 16:50-17:30: [https://etherpad.openstack.org/p/servicevm Service VM Discussion]

== Nova ==

'''Wednesday, May 14'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-third-party-ci Continuation of third party CI]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support Clustered hypervisor support in Nova]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-deprecating-baremetal The road to deprecating nova.virt.baremetal]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-data-transfer-service Data transfer service plug-in]
* 1:50pm [https://etherpad.openstack.org/p/juno-nova-live-upgrade Next steps in live upgrade]
* 2:40pm [https://etherpad.openstack.org/p/juno-nova-image-precaching Image precaching service]
* 3:30pm [https://etherpad.openstack.org/p/juno-nova-flavor-storage-revamp Flavor storage re-vamp]
* 4:30pm [https://etherpad.openstack.org/p/juno-nova-cross-project-interactions Rethinking cross project interactions]
* 5:20pm [https://etherpad.openstack.org/p/juno-nova-v2-on-v3-api-poc Nova V2 on V3 API implementation POC]

'''Thursday, May 15'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-hypev-new-features Hyper-V Driver new features]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-libvirt-driver-roadmap Libvirt driver roadmap for Juno]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-kvm-live-migration Improve performance of live migration on KVM]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-conductor-api limited conductor API]
* 1:30pm [https://etherpad.openstack.org/p/juno-nova-quota-state-management Implementing state management for quotas]
* 2:20pm [https://etherpad.openstack.org/p/juno-nova-multi-volume-snapshots Multi-Volume Snapshots]
* 3:10pm [https://etherpad.openstack.org/p/juno-nova-hypervisor-power-mgmt Hypervisor power management]
* 4:10pm [https://etherpad.openstack.org/p/juno-nova-sriov-support SR-IOV support]
* 5:00pm [https://etherpad.openstack.org/p/juno-nova-v3-api Nova V3 API]

'''Friday, May 16'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-vmware-driver-roadmap Vmwareapi driver roadmap for Juno]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-docker-driver-features Docker driver - features & testing]
* 10:50am [https://etherpad.openstack.org/p/juno-nova-gantt-apis Future of Gantt APIs and interfaces]
* 11:40am [https://etherpad.openstack.org/p/juno-nova-no-db-scheduler Common no DB Scheduler]
* 1:20pm [https://etherpad.openstack.org/p/juno-nova-scheduling-server-groups Simultaneous Scheduling for Server Groups]
* 2:10pm [https://etherpad.openstack.org/p/juno-nova-scheduler-hints-vm-lifecycle Scheduler hints for VM life cycle]
* 3:00pm [https://etherpad.openstack.org/p/juno-nova-devops Nova Dev/Ops Session]
* 4:00pm [https://etherpad.openstack.org/p/juno-nova-unsession Unsession]

== Ops ==
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]

* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]
* Fri 4:00 – 4:40 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]
* Fri 4:50 – 5:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]

== Oslo ==
* Wed 9:00 - 9:40 [https://etherpad.openstack.org/p/juno-oslo-release-plan Release Plan for Low-level Libraries]
* Wed 9:50 - 10:30 oslo.messaging status and plans for Juno
* Wed 11:00 - 11:40 [https://etherpad.openstack.org/p/olso.messaging_amqp_1.0 AMQP 1.0 protocol driver]
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session
* Thu 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-infra-library-testing Testing pre-releases of Oslo libs with apps]
* Thu 11:00 - 11:40 [https://etherpad.openstack.org/p/juno-osprofiler OpenStack cross service/project OpenStack profiler]
* Thu 15:10 - 16:00 [https://etherpad.openstack.org/p/juno-oslo-bayer Upstream chat with Mike Bayer]
* Thu 16:10 - 17:00 [https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy rpc proxy(oslo.messaging)]
* Fri 14:10 - 15:50 [https://etherpad.openstack.org/p/juno-summit-oslo-rootwrap oslo.rootwrap: performance and other improvements]
* Fri 15:00 - 16:40 Semantic versioning and oslo
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-pki-for-messaging PKI for messaging]

== QA ==

'''Wednesday'''
* 2:40 – 3:20 [https://etherpad.openstack.org/p/juno-summit-branchless-tempest Branchless Tempest]
* 3:30 – 4:10 [https://etherpad.openstack.org/p/juno-summit-tempest-documentation Tempest Documentation Gaps]
* 4:30 – 5:10 Functional API Testing - post dev QA vs TDD
* 5:20 – 6:00 [https://etherpad.openstack.org/p/juno-rally-and-tempest Rally and Tempest Integration]

'''Thursday'''
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]
* 2:20 – 3:00 [https://etherpad.openstack.org/p/juno-summit-negative-fuzzy-testing Negative Testing: Fuzzy Test Framework]
* 3:10 – 3:50 [https://etherpad.openstack.org/p/juno-summit-improve-ux-tools How to improve the UX of our Testing Tools]
* 4:10 – 4:50 [https://etherpad.openstack.org/p/juno-summit-tempest-gui-client-server Tempest, GUI, Client, Server]

'''Friday'''
* 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-grenade Grenade Current Status and Next Steps]
* 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]

== Release Management ==

* Wednesday 1:50pm [https://etherpad.openstack.org/p/juno-summit-release-branches Release branches, QA and requirements]
* Thursday 9:00am [https://etherpad.openstack.org/p/juno-summit-vmt Vulnerability management in Juno]
* Thursday 5:00pm [https://etherpad.openstack.org/p/StableIcehouse Stable branches maintenance]
* Friday 3:00pm [https://etherpad.openstack.org/p/juno-summit-release-schedule Juno release schedule and processes]
* Friday 4:50pm [https://etherpad.openstack.org/p/juno-summit-feedback Design Summit feedback]

== Sahara (ex. Savanna) ==

* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]

== Swift ==
== TripleO (Deployment) ==
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]
* Fri 13:20 - 14:00 [https://etherpad.openstack.org/p/juno-summit-tripleo-environment TripleO Development and Testing Environment]
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]

== Trove ==
== User Committee ==
== Other Projects ==
* [http://junodesignsummit.sched.org/event/6f9fe2ec2e6d3843139663a350cdc511 Tue 17:30 - 18:10] [https://etherpad.openstack.org/p/juno-summit-discovery-and-diagnostic-for-openstack Discovery and Diagnostic for OpenStack]
* [http://junodesignsummit.sched.org/event/ab6d8eed3c6fd85dc450c099aba22e11 Tue 12:05 - 12:45] [https://etherpad.openstack.org/p/juno-design-summit-designate-session-1 Designate Session 1]

Horizon/WebAccessibility

2014-05-07T22:31:40Z

Doug Fish:

* What do we mean by accessibility?
** http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
** http://www.w3.org/TR/WCAG20/
** http://www-03.ibm.com/able/guidelines/web/accessweb.html This IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.

* Testing Techniques
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface. You should be able to reach and activate all of Horizon's functions this way. You should always be able to see the focus. The tabbing should happen in a logical order. I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.

http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast). Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users. Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.

* WAI-ARIA
WAI-ARIA is a specification that lets rich web applications (Like the Horizon Dashboard!) specify the meaning of HTML elements when they are used in a manner that isn't automatically implied by the tag being used. So if you are displaying a button and you are using a <button> or <input type="button"> html element no extra work is needed. However, if you are displaying a button and its constructed out of <div> elements you're going to need to use WAI-ARIA tagging so that assistive technology - especially screen readers can use it. Here's a useful introduction: http://rawgit.com/w3c/aria-in-html/master/index.html

* Screen readers
I'm still looking into screen readers that will be useful in our environments. I'm thinking specifically of
** http://www.nvaccess.org/
** https://wiki.gnome.org/Projects/Orca

* Underlying components
One of our challenges with Horizon is that some of the components we build on may not be accessible. This will likely show up more clearly in our testing with keyboard + screen readers. I expect the process will be that we will find some problem. We willl look at where the improper markup/CSS is generated, and find its not generated directly by Horizon but maybe by django, bootstrap, or some other outside code.

I see that bootstrap claims accessibility (well bootstrap 3 does anyway) [http://getbootstrap.com/getting-started/#accessibility] but I find it curious that there is a bootstrap accessibility plugin [https://www.paypal-engineering.com/2014/01/28/bootstrap-accessibility-plugin-making-the-popular-web-development-framework-better]. Not sure if we are going to need it.

Our calendar widget is clearly not accessible. (I think this widget has i18n problems too)

For each component we find problems in we'll have to determine if there is another suitable component that supports accessibile, if we can workaround the problem, or if this is best handled by contributing to the component itself.

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

Horizon/WebAccessibility

2014-05-07T21:30:06Z

Doug Fish:

* What do we mean by accessibility?
** http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
** http://www.w3.org/TR/WCAG20/
** http://www-03.ibm.com/able/guidelines/web/accessweb.html This IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.

* Testing Techniques
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface. You should be able to reach and activate all of Horizon's functions this way. You should always be able to see the focus. The tabbing should happen in a logical order. I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.

http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast). Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users. Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.

* WAI-ARIA
WAI-ARIA is a specification that lets rich web applications (Like the Horizon Dashboard!) specify the meaning of HTML elements when they are used in a manner that isn't automatically implied by the tag being used. So if you are displaying a button and you are using a <button> or <input type="button"> html element no extra work is needed. However, if you are displaying a button and its constructed out of <div> elements you're going to need to use WAI-ARIA tagging so that assistive technology - especially screen readers can use it. Here's a useful introduction: http://rawgit.com/w3c/aria-in-html/master/index.html

* Screen readers
I'm still looking into screen readers that will be useful in our environments. I'm thinking specifically of
** [http://www.nvaccess.org/]
** [https://wiki.gnome.org/Projects/Orca]

* Underlying components
One of our challenges with Horizon is that some of the components we build on may not be accessible. This will likely show up more clearly in our testing with keyboard + screen readers. I expect the process will be that we will find some problem. We willl look at where the improper markup/CSS is generated, and find its not generated directly by Horizon but maybe by django, bootstrap, or some other outside code.

I see that bootstrap claims accessibility (well bootstrap 3 does anyway) [http://getbootstrap.com/getting-started/#accessibility] but I find it curious that there is a bootstrap accessibility plugin [https://www.paypal-engineering.com/2014/01/28/bootstrap-accessibility-plugin-making-the-popular-web-development-framework-better]. Not sure if we are going to need it.

Our calendar widget is clearly not accessible. (I think this widget has i18n problems too)

For each component we find problems in we'll have to determine if there is another suitable component that supports accessibile, if we can workaround the problem, or if this is best handled by contributing to the component itself.

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

Horizon/WebAccessibility

2014-05-07T18:01:28Z

Doug Fish:

* What do we mean by accessibility?
** http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
** http://www.w3.org/TR/WCAG20/
** http://www-03.ibm.com/able/guidelines/web/accessweb.html This IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.

* Testing Techniques
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface. You should be able to reach and activate all of Horizon's functions this way. You should always be able to see the focus. The tabbing should happen in a logical order. I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.

http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast). Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users. Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.

* WAI-ARIA
WAI-ARIA is a specification that lets rich web applications (Like the Horizon Dashboard!) specify the meaning of HTML elements when they are used in a manner that isn't automatically implied by the tag being used. So if you are displaying a button and you are using a <button> or <input type="button"> html element no extra work is needed. However, if you are displaying a button and its constructed out of <div> elements you're going to need to use WAI-ARIA tagging so that assistive technology - especially screen readers can use it. Here's a useful introduction: http://rawgit.com/w3c/aria-in-html/master/index.html

* Screen readers
I'm still looking into screen readers that will be useful in our environments. I'm thinking specifically of
** http://www.nvaccess.org/
** https://wiki.gnome.org/Projects/Orca

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

Horizon/WebAccessibility

2014-05-05T14:39:24Z

Doug Fish:

Horizon/WebAccessibility

2014-05-02T19:08:21Z

Doug Fish:

Horizon/WebAccessibility

2014-04-24T14:17:10Z

Doug Fish:

Horizon/WebAccessibility

2014-04-24T14:16:33Z

Doug Fish:

* What do we mean by accessibility?
http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
http://www.w3.org/TR/WCAG20/
http://www-03.ibm.com/able/guidelines/web/accessweb.html This IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

Horizon/WebAccessibility

2014-04-24T14:15:47Z

Doug Fish:

* What do we mean by accessibility?
http://www-03.ibm.com/able/access_ibm/disability.html

* So what exactly is expected?
http://www.w3.org/TR/WCAG20/
The following IBM link is heavily based on the w3 link above. I've included it because I've found the recent guidance, explanations, and examples to be useful.
http://www-03.ibm.com/able/guidelines/web/accessweb.html

* Known Issues:
We inspected the Horizon (Havana release) for web accessibility and found the following problems.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents]
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html 1.3.1 Info and Relationships]
** There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
** There is no scope attribute in th elements.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)]
** text color and background color in the left menu
** text color and background color in the top menu
** link color and background color in the main content area
** text color and background color of the some buttons

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard]
** It's not easy to handle the layered message window by keyboard only.
** It may be difficult for a blind person to notice this layered error message.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks]
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order]
** The order of navigation doesn't match the visual order in some cases.
** The focus movement is not restricted to the layered pop-up window.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page]
** There is no lang attribute on the html element.

* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html 3.3.2 Labels or Instructions]
** Is it better to use label element to associate text labels with input elements?

Meetings/Horizon

2014-03-19T15:40:42Z

Doug Fish: /* Agenda for next meeting (March 18) */

Meetings/Horizon

2014-03-19T15:39:33Z

Doug Fish:

The [[OpenStack]] Horizon Team holds public meetings in #openstack-meeting-3. Everyone is encouraged to attend.
* Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=16&min=0&sec=0 16:00 UTC]

== Apologies for absense ==
* jpich (March 18th)

== Agenda for next meeting (March 18) ==

=== Icehouse RC1 ===

https://launchpad.net/horizon/+milestone/icehouse-rc1

=== Design Summit Session Topics ===

Summit topic suggestion is open for the Juno summit. http://summit.openstack.org/

The announcement http://lists.openstack.org/pipermail/openstack-dev/2014-March/029319.html

Cross-project sessions are available this time around as well.

== Agenda for next meeting (March 25) ==

=== Translation and String Freeze ===
Let's talk through the upcoming String Freeze and how we will manage changes to the user facing strings after the freeze.
Does this reflect our process: [[StringFreeze|https://wiki.openstack.org/wiki/StringFreeze]] ?

== Previous meetings ==

http://eavesdrop.openstack.org/meetings/horizon/

Meetings/Horizon

2014-03-19T15:38:20Z

Doug Fish: /* Agenda for next meeting (March 18) */

The [[OpenStack]] Horizon Team holds public meetings in #openstack-meeting-3. Everyone is encouraged to attend.
* Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=16&min=0&sec=0 16:00 UTC]

== Apologies for absense ==
* jpich (March 18th)

== Agenda for next meeting (March 18) ==

=== Icehouse RC1 ===

https://launchpad.net/horizon/+milestone/icehouse-rc1

=== Design Summit Session Topics ===

Summit topic suggestion is open for the Juno summit. http://summit.openstack.org/

The announcement http://lists.openstack.org/pipermail/openstack-dev/2014-March/029319.html

Cross-project sessions are available this time around as well.

== Agenda for next meeting (March 24) ==

=== Translation and String Freeze ===
Let's talk through the upcoming String Freeze and how we will manage changes to the user facing strings after the freeze.
Does this reflect our process: [[StringFreeze|https://wiki.openstack.org/wiki/StringFreeze]] ?

== Previous meetings ==

http://eavesdrop.openstack.org/meetings/horizon/