- Community - lists.openinfra.dev

Re: [openstack-community] Openstack Diversity Working Group
by Barrett, Carol L 11 Jun '15

11 Jun '15

The Doodle time zone doesn't seem to be appearing in the local timebased upon the viewer. Sorry - The time zone is US/Pacific time (UTC-7), you'll need to do your own conversion. Thanks Carol From: Sousou, Imad [mailto:imad.sousou@intel.com] Sent: Tuesday, June 09, 2015 11:34 AM To: foundation(a)lists.openstack.org; openstack(a)lists.openstack.org; community(a)lists.openstack.org; foundation-board(a)lists.openstack.org; openstack-dev(a)lists.openstack.org Subject: [OpenStack Foundation] Openstack Diversity Working Group Stackers - We're happy to announce the creation of a Diversity Working Group. The genesis for this work group was a discussion at the May meeting of the OpenStack Board of Directors ahead of the Vancouver Summit. The Board is committed to fostering an inclusive and welcoming place for all people to collaborate to drive innovation and design cutting-edge data center capabilities, while finding the best answers to our most pressing challenges. To achieve this, the Board formed this Work Group to determine what actions are required to fulfill this commitment. Three Board members volunteered to work with community members in this Work Group and bring updates/requests to the Board for discussion and action on a regular basis, starting with the July meeting. If you're interested in joining this effort, please: * Join the Foundation mail list to participate in discussions and shape the direction: click here<http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation> * Visit the wiki page for this work group to learn more about the charter: click here<https://wiki.openstack.org/wiki/Diversity> * Plan to join the kick-off IRC meeting and let us know what day/times work for you by accessing the Doodle here: click here<http://doodle.com/z85c23dtexx8qzq7> We will send out the results of the Doodle to the mail list and look forward to working with you to foster a strong and diverse community. Thanks Imad Sousou (Intel), Egle Sigler (Rackspace), Kavit Munshi (Aptira)

3 4

[openstack-community] OpenStack Community Weekly Newsletter (May 29 - June 5)
by Stefano Maffulli 05 Jun '15

05 Jun '15

1 0

[openstack-community] [upstream] Vancouver upstream training session debrief
by Stefano Maffulli 03 Jun '15

03 Jun '15

Hello folks, first of all thank you to all instructors and volunteer staff and mentors that helped in Vancouver: this program would not be possible without the kind donations of your time and effort. I'd like to collect notes and comments on what went well and what should be changed for the next events. I'll start (quite long): Slides & content ================ - I think the rst format and common repository worked well. We miss one (set of) slides to illustrate the whole 2 days program. Maybe copying the content over from the wiki Info page[1] to the index.rst page would be a good thing. - the index.rst is not formatted properly. Christian Berendt is working on this and may need a help from sphinx/hieroglyph gurus https://review.openstack.org/#/c/185946/ - the draft site[2] is great. I think that keeping the slides in /draft/ is good enough since the status of those slides may not be always up to date with the authoritative source of information like governance.o.o or infra/manual - with the slides in .rst format and in a git repo, I think they could be hooked to a translation system. I'd consider hooking up and translate the material in other languages. Japanese would be the most likely candidate, and people from China have expressed also interest. - suggestions and commentts from the participants: + Maybe work through some more demos - ie, run through committing a change to sandbox doing it "live" from the presenter desk + Point out the differences between docs and code reviews - environment prerequisites + Talk about gating checks - ie, what the automated checks are actually checking for. + It might be worth considering recording it and making it like a Coursera course or a Kahn Academy course. + The slideshow can improved. It should contain more graphics (ex: apc/atc relation), clickable links (ex: stackforge). + It would be great to collect a list of bugs which are really "low hanging" fruits, so that they can be solved during the two days. + Teach about the source code. How it's organized? Why is it so? After rpm/deb packaging, where do files go on the root filesystem? How do I run tests? How do I write my own tests? What if I need to introduce a new file? How are the python packages arranged? How do subprograms communicate to each other? + consider separating software developers and technical writers One more comment led me to believe that we have not done a good job at communicating that the training is 2 days live + mentoring sessions afterwards. See below for ideas on how to fix this. Administrative process ====================== - Planning attendance is hard. Of the 85+ people who originally signed up, about 45 showed up. I noticed that about 10 people removed themselves when we started sending notifications in preparation to the live session. I think that the barrier to sign up is too low and we can raise it so that only highly motivated people sign up to attend. The low barrier also makes it hard for people to read and understand that the training is 2 days live + online mentoring afterwards. + To set the bar higher, I think we need to find a way to scale the method used by Loic. He engages with every applicant immediately, as they sign up, and if they don't respond to his solicitations he removes them from the list. That's very intense and time consuming but ends up getting more motivated people. I think this can be scaled by having a larger pool of mentors that gets to solicit applicants. A form of light automation using Google Forms and Trello (with glue provided by zapier.com) may be enough? Needs experimenting. + To make it clear that the training is 2 days + live sessions I think we should have people engage with mentors and set dates for meetings *before* the training starts. - I think the Trello board is a good step forward: it allows staff and management to follow progress of each student. Format ====== - I'm starting to think that to days is probably too much for some people. The comments I have received from the survey are all extremely positive but a couple of written comments make me believe that trying to shorten the class to 1 day and 1 extra day for custom deep dives would probably give more value. This deserves a thread on its own. Venue & logistics ================= - Participants and staff should have their names printed to facilitate social interactions - Renting the Legos was the best idea ever. Definitely worth considering for the future. Thanks again, stef [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Training/Info [2] http://docs.openstack.org/draft/upstream-training/#1

5 5

[openstack-community] [Wiki] Packstack
by Shinobu Kinjo 02 Jun '15

02 Jun '15

Hi, I am thinking of updating packstack wiki page which is: https://wiki.openstack.org/wiki/Packstack Would any of you tell me what I should / have to do first to update that page? Because I'm not 100% sure which mailing list I have to send about that question, I just email both lists of openstack and community. Thanks! Kinjo -- Life w/ Linux <http://i-shinobu.hatenablog.com/>

2 2

[openstack-community] OpenStack Community Weekly Newsletter (May 8 - 22)
by Stefano Maffulli 30 May '15

30 May '15

1 0

[openstack-community] AUTO: Jeff Bendorf/Denver/IBM is out of the office. (returning 06/08/2015)
by Jeff Bendorf 29 May '15

29 May '15

I am out of the office until 06/08/2015. If this is urgent, please contact my manager Roger Widholm at 1-818-539-3184 or email rwidholm(a)us.ibm.com. Note: This is an automated response to your message "Community Digest, Vol 34, Issue 16" sent on 05/29/2015 6:00:02. This is the only notification you will receive while this person is away.

1 0

Re: [openstack-community] OSCON: Call for proposals for Open Cloud Day, deadline to submit your proposals is tomorrow May 29th
by Denise Ridolfo 28 May '15

28 May '15

Hi Everyone, A friendly reminder: Don’t forget to submit your OpenStack proposals for Open Cloud Day at OSCON – the deadline is tomorrow, May 29th! Best regards, Denise Denise Ridolfo Marketing Consultant On behalf of the OpenStack Foundation From: Denise Ridolfo Consultancy <ridolfodenise(a)gmail.com> Date: Thursday, May 7, 2015 at 3:16 AM To: OpenStack Marketing Mailing List <marketing(a)lists.openstack.org>, OpenStack Community List <community(a)lists.openstack.org> Cc: Denise Ridolfo Consultancy <ridolfodenise(a)gmail.com> Subject: OSCON: Call for proposals for Open Cloud Day and Ignite - now is the time to send in your OpenStack submissions Hi Everyone, Just a quick email to let you know that there is a new call out for OSCON Open Cloud Day & Ignite proposal submissions. Here are the details: OSCON - Open Cloud Day Tuesday, July 21, 2015 at the Oregon Convention Center Deadline: midnight on May 29, 2015 Link to submit your proposal: http://www.oscon.com/open-source-2015/public/cfp/395 * Open Cloud Day is an all-day event focused on the State of Cloud in 2015, co-sponsored by Red Hat & IBM * They are specifically looking for proposals on these topics: Open Source, IssS, PaaS, Linux Containers, Sofware Defined Networking, and lessons learned in deploying new and rapidly changing technologies * This is a 30 minute presentation for a developer audience focused on the next-generation of scale-out applications in a software defined infrastructure Ignite OSCON Monday, July 20, 2015 located in the Portland Ballroom at the Oregon Convention Center Deadline: midnight on June 5, 2015 Link to submit your proposal: http://www.oscon.com/open-source-2015/public/cfp/397 * Any topic is fair game as long as it’s interesting * - * from technology to culture to business to science fiction * This is a 5-minute presentation to deliver something inspirational, lessons learned, or an interesting story * Speakers are limited to 20 slides, which automatically advance after 15 seconds—that’s the fun of Ignite! Act now to send in your OpenStack submissions! Best regards, Denise Ridolfo Marketing Consultant On behalf of the OpenStack Foundation

1 0

[openstack-community] Installataion of Openstack (network setup ) with vlan interface
by pra devOPS 25 May '15

25 May '15

All: I am having problem settinup the network on openstack wiht ml2 plugin. Below is my configuration. I have a vlan interface which has a IP 1.2.3.4. and I have a phsysical interface which is assocaited to that box (that does not have an IP). Below is How they look like VLAN1 (VLAN ) Physical Device Configuration ------------ ---------------------------------- VLAN=yes TYPE=Ethernet TYPE=Vlan BOOTPROTO=dhcp PHYSDEV=phynet1 DEFROUTE=yes VLAN_ID=1 PEERDNS=yes REORDER_HDR=0 PEERROUTES=yes BOOTPROTO=static IPV4_FAILURE_FATAL=no DOMAIN=eng.myorg.com IPV6INIT=yes DEFROUTE=yes IPV6_AUTOCONF=yes IPV4_FAILURE_FATAL=no IPV6_DEFROUTE=yes IPV6INIT=no IPV6_PEERDNS=yes IPV6_AUTOCONF=yes IPV6_PEERROUTES=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_FAILURE_FATAL=no NAME=phynet1 NAME=VLAN1 UUID=5ba6c8d1-8fe7-3fec-ae8c-ad67081547dc UUID=9cbf88dc-456c-1234-9876-12bece795678 DEVICE=phynet1 ONBOOT=yes ONBOOT=no DEVICE=MyVLAN1 IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPADDR=1.2.3.4 PREFIX=32 GATEWAY=1.2.3.1 DNS1=1.2.9.5 PEERDNS=yes PEERROUTES=yes I added the br-ex and br-int , And added port VLAN1 to br-ex. But I dont see the br-ex and br-int interfaces when I do ifconfig. Can somebody advice how to setup the network on openStack with above settings/. I am kind of stuck. Thanks, S

2 1

[openstack-community] Montreal Openstack Meetup: Tuesday May 26th - NFV and SDN
by Marcos Garcia 23 May '15

23 May '15

Hello everybody It is my pleasure to announce in the Openstack mailing list the next Meetup in Montreal (Canada). This time, a NFV and SDN special. It will be held in the UQAM Pavillon Kennedy (room PK-1140) at 6 p.m. Metro Place des Arts. Details for the venue can be found here: http://montrealopenstack.org/en/7th-openstack-montreal-meeting/ It is the first time that we use this ML as we were running the event a bit in 'beta' mode. Now it's our 7th show, and we feel confident to receive all sorts of people So if any of you live close to Montreal downtown, don't hesitate to come visit! Snacks and beverages are provided this time by courtesy of Red Hat Canada. Regards! -- Marcos Garcia Senior Solution Offering Architect; RHCE, RHCVA, ITIL Cloud Innovation Practice - Red Hat Canada, Inc Cell: 514 794 2207 mgarciam(a)redhat.com

1 0

[openstack-community] OpenStack installation
by pra devOPS 22 May '15

22 May '15

Hi All: Hi All: I am installing Icehouse Openstack all in one machine with one single vlan interface (binded to a physical interface), I am facing the problem while executing the neturon commnads, but keystone,glance and few nova commands works fine ,But nova commands related to network and neutron ommands gives 401 Error. Can some one please help me. . Below is my configurations,First interface configurtaoins Interface configuration: VLAN1 (VLAN ) Physical Device Configuration ------------ ---------------------------------- VLAN=yes TYPE=Ethernet TYPE=Vlan BOOTPROTO=dhcp PHYSDEV=phynet1 DEFROUTE=yes VLAN_ID=1 PEERDNS=yes REORDER_HDR=0 PEERROUTES=yes BOOTPROTO=static IPV4_FAILURE_FATAL=no DOMAIN=eng.myorg.com IPV6INIT=yes DEFROUTE=yes IPV6_AUTOCONF=yes IPV4_FAILURE_FATAL=no IPV6_DEFROUTE=yes IPV6INIT=no IPV6_PEERDNS=yes IPV6_AUTOCONF=yes IPV6_PEERROUTES=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_FAILURE_FATAL=no NAME=phynet1 NAME=VLAN1 UUID=5ba6c8d1-8fe7-3fec-ae8c-ad67081547dc UUID=9cbf88dc-456c-1234-9876-12bece795678 DEVICE=phynet1 ONBOOT=yes ONBOOT=no DEVICE=MyVLAN1 IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPADDR=1.2.3.4 PREFIX=32 GATEWAY=1.2.3.1 DNS1=1.2.9.5 PEERDNS=yes PEERROUTES=yes I got the keystone installed and working ( all keystone commands work). Below is the example: keystone user-list +----------------------------------+---------+---------+-------------------------+ | id | name | enabled | email | +----------------------------------+---------+---------+-------------------------+ | 04e35d08fcfc472ab50801f1c188a7b0 | admin | True | myname(a)myrog.com | 9d46f9a3082448daa2dad3de3e754d92 | glance | True | myname(a)myrog.com | | 937dbd7372bb4c92a207a9f415d062c6 | neutron | True | myname(a)myrog.com | | a4e28e658d784000862dc4503c9b0003 | nova | True | myname(a)myrog.com | | 04bba2d189b341c88bf2765db0ae05db | myname | True | myname(a)myrog.com | +----------------------------------+---------+---------+-------------------------+ Got Glance installed and working (it gives empty results as I dont have the images which is fine with me ) glance image-list +----+------+-------------+------------------+------+--------+ | ID | Name | Disk Format | Container Format | Size | Status | +----+------+-------------+------------------+------+--------+ installed nova-api and nova image-list also works gives empty results which is fine with me . nova image-list +----+------+--------+--------+ | ID | Name | Status | Server | +----+------+--------+--------+ +----+------+--------+--------+ But When I try to do some other commands wiht NOVA I get 400 error like below: nova net-list ERROR: The server could not comply with the request since it is either malformed or otherwise incorrect. (HTTP 400) (Request-ID: req-b25d79ae-8739-49ff-8fa6-a8ed1d078e7b) Attahced nova-net-list.log (this has the debug version of above command ) All neutron commands gives me error like below Authentication required Attached the file neutron-net-list.log which has the debug version of the above command.Also I see same mulitple requests to the same endpoints. if I do ifconfig, i dont see the networks I configured br-ex and br-int on the same single ip. How do I see them, I just installed it till neutron did not go further as I was getting the Authentcation problem. NOTE:While running the neutron and nova commands I sources all the OS keystone parameters. Also attached the keystone,glance,nova and neutron conf files and tenants,users,services,endpoints configured in keystone AND Give below in email as well. Keystone env variables: export OS_USERNAME=admin export OS_PASSWORD=mypassword export OS_TENANT_NAME=admin export OS_AUTH_URL=http://1.2.3.4:35357/v2.0 nova.conf rpc_backend = qpid qpid_hostname = 1.2.3.4 my_ip = 1.2.3.4 vncserver_listen = 1.2.3.4 vncserver_proxyclient_address = 1.2.3.4 auth_strategy = keystone network_api_class = nova.network.neutronv2.api.API neutron_url = http://1.2.3.4:9696 neutron_auth_strategy = keystone neutron_admin_tenant_name = service neutron_admin_username = nova neutron_admin_password = nova123 neutron_admin_auth_url = http://1.2.3.4:35357/v2.0 linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver firewall_driver = nova.virt.firewall.NoopFirewallDriver security_group_api = neutron service_neutron_metadata_proxy = true neutron_metadata_proxy_shared_secret = myOSsetUp [keystone_authtoken] auth_uri = http://1.2.3.4:5000 auth_host = 1.2.3.4 auth_protocol = http auth_port = 35357 admin_user = nova admin_tenant_name = service admin_password = nova123 Neutron.conf [DEFAULT] auth_strategy = keystone rpc_backend = neutron.openstack.common.rpc.impl_qpid qpid_hostname = 1.2.3.4 notify_nova_on_port_status_changes = True notify_nova_on_port_data_changes = True nova_url = http://1.2.3.4:8774/v2 nova_admin_username = nova nova_admin_tenant_id = 1ecb20c295a04b45b19f88bed22fd9f8 nova_admin_password = nova123 nova_admin_auth_url = http://1.2.3.4:35357/v2.0 core_plugin = ml2 service_plugins = router [keystone_authtoken] auth_uri = http://1.2.3.4:5000 auth_host = 1.2.3.4 auth_protocol = http auth_port = 35357 admin_tenant_name = service admin_user = neutron admin_password = neutron123 metadata_agent.ini auth_url = http://1.2.3.4:5000/v2.0 auth_region = regionOne # Turn off verification of the certificate for ssl # auth_insecure = False # Certificate Authority public key (CA cert) file for ssl # auth_ca_cert = admin_tenant_name = service admin_user = neutron admin_password = neutron123 nova_metadata_ip = 1.2.3.4 metadata_proxy_shared_secret = myOSsetUp Keystone Outputs: keystone tenant-list +----------------------------------+---------+---------+ | id | name | enabled | +----------------------------------+---------+---------+ | 0f3e717860444ca9bda45710940de033 | admin | True | | f01c350959d24c63a467cea3875ba9f8 | demo | True | | 1ecb20c295a04b45b19f88bed22fd9f8 | service | True | +----------------------------------+---------+---------+ keystone service-list +----------------------------------+----------+----------+----------------------+ | id | name | type | description | +----------------------------------+----------+----------+----------------------+ | 838524a98a8b45a7961615ace1d65576 | glance | image | Image Service | | 4e97c66d9be64056a63bdc6469b0cabf | keystone | identity | OpenStack Identity | | 0f569363f59444d88aaf32589307c1b1 | neutron | network | OpenStack Networking | | ae4e5d0cd58e4bf6bfe71a861ff3db32 | nova | compute | OpenStack Compute | +----------------------------------+----------+----------+----------------------+ keystone eddpoint-list +----------------------------------+-----------+--------------------------------------------+--------------------------------------------+--------------------------------------------+----------------------------------+ | id | region | publicurl | internalurl | adminurl | service_id | +----------------------------------+-----------+--------------------------------------------+--------------------------------------------+--------------------------------------------+----------------------------------+ | 467f893cb1c848a2bb98826895bc7a35 | regionOne | http://1.2.3.4:9696 | http://1.2.3.4:9696 | http://1.2.3.4::9696 | 0f569363f59444d88aaf32589307c1b1 | | a47f40ebadbc454e8e56ff976fc43ca6 | regionOne | http://1.2.3.4:8774/v2/%(tenant_id)s | http://1.2.3.4:8774/v2/%(tenant_id)s | http://1.2.3.4:8774/v2/%(tenant_id)s | ae4e5d0cd58e4bf6bfe71a861ff3db32 | | bdca2ca89ad6423caa47fc5ef6e7a34c | regionOne | http://1.2.3.4:5000/v2.0 | http://1.2.3.4:5000/v2.0 | http://1.2.3.4:35357/v2.0 | 4e97c66d9be64056a63bdc6469b0cabf | | e71ea58bafae4c818577e74bbf26e002 | regionOne | http://1.2.3.4:9292/v2.0 | http://1.2.3.4:9292/v2.0 | http://1.2.3.4:9292/v2.0 | 838524a98a8b45a7961615ace1d65576 | +----------------------------------+-----------+--------------------------------------------+--------------------------------------------+--------------------------------------------+----------------------------------+ keystone user-list +----------------------------------+---------+---------+-------------------------+ | id | name | enabled | email | +----------------------------------+---------+---------+-------------------------+ | 04e35d08fcfc472ab50801f1c188a7b0 | admin | True | myname(a)myrog.com | | 9d46f9a3082448daa2dad3de3e754d92 | glance | True | myname(a)myrog.com | | 937dbd7372bb4c92a207a9f415d062c6 | neutron | True | myname(a)myrog.com | | a4e28e658d784000862dc4503c9b0003 | nova | True | myname(a)myrog.com | | 04bba2d189b341c88bf2765db0ae05db | myname | True | myname(a)myrog.com | +----------------------------------+---------+---------+-------------------------+

1 0