Re: [openstack-dev] [api] Forming the API Working Group

2014-10-11 Thread Jay Pipes
Thanks for getting this going, Everett! Comments inline... On 10/08/2014 07:05 PM, Everett Toews wrote: This is the start of the API Working Group (API WG). yay! :) To avoid bike shedding over the name of the working group, I decided to

[openstack-dev] [Heat][Trove][Horizon][Glance] New Juno RCs available

2014-10-11 Thread Thierry Carrez
Hello everyone, Due to various issues discovered in the published 2014.2 release candidates, we regenerated new Juno release candidates for Heat, Trove, Horizon and Glance. You can find the list of bugfixes in these RCs and links to source tarballs at:

[openstack-dev] Starting iSCSI initiator service iscsid failed while installing Devstack

2014-10-11 Thread Nitika
Hi, I'm trying to install devstack on Ubuntu but getting the following error : Please note that I'm not using any proxy to access the internet. After this operation, 0 B of additional disk space will be used. Setting up open-iscsi (2.0.871-0ubuntu9.12.04.2) ... update-rc.d: warning: open-iscsi

Re: [openstack-dev] [api] Forming the API Working Group

2014-10-11 Thread Preston L. Bannister
Tricky. First, I am new to OpenStack, and as such tend to want to shut-up and listen. Second, I have done APIs for distributed systems for over 30 years. Yes, I got in very early. As such I am guilty of or saw lots of bad examples. Also I found patterns that worked very well. That said, the

[openstack-dev] [neutron] Can Neutron VPNaaS work with strongswan? (Openswan removed from Debian)

2014-10-11 Thread Thomas Goirand
Hi, As you may know, OpenSwan has been largely unmaintained in Debian, and then was removed from Testing, and then Sid last summer. OpenSwan had some unaddressed security issues, and removing it from Debian was IMO the correct thing to do. Ubuntu followed, and Utopic doesn't have OpenSwan anymore

Re: [openstack-dev] [oslo] zeromq work for kilo

2014-10-11 Thread Li Ma
On 2014/9/17 22:34, Doug Hellmann wrote: The documentation in the oslo.messaging repository [2] would be a good place to start for that. If we decide deployers/operators need the information we can either refer to it from the guides managed by the documentation team or we can move/copy the