Re: [Openstack] [GLANCE] Ready to move to GitHub/Gerrit?
Right now i will take anything but prefer rpms. :) Here ya go :) http://yum.griddynamics.net/yum/master/openstack/ Jan, take you risk and try these RPMs on CentOS 6. Feel free to provide a feedback to me. We tested our RPMs on RHEL 6.1 x86_64. Our Diablo-3 branch is almost ready for release: http://yum.griddynamics.net/yum/diablo-3/openstack/ It's under QA now and should be released at the end of this week. Andrey Brindeyev Grid Dynamics, Development Manager abrinde...@griddynamics.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Nova/Keystone integration and /usr/bin/nova
Hi all! Is /usr/bin/nova supposed to work when you enable Keystone integration in Nova? Me got following: # nova list 'x-server-management-url' # nova show 1 'x-server-management-url' strace output: recvfrom(3, 305 Use Proxy\n\nThe resource must..., 136, 0, NULL, NULL) = 136 Andrey Brindeyev Grid Dynamics, Development Manager abrinde...@griddynamics.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Do we need SSL on nova-api ports?
More practical question: Should we use the same ports for SSL-enabled services as we have for plain-HTTP now (8773/8774)? If not, which ones should I choose for my SSL-protected Nova installation? Of course I can choose any on my own system - the question is - should we agree which ports will be OFFICIAL while using SSL on Nova installations across the globe? That's will be easy for community (at least to distingush between non-SSL and SSL setup in logs/etc). Andrey. 02.05.2011, в 16:42, Vishvananda Ishaya написал(а): Can we do this with a flag (or two) and just keep regular http if the flag is not set? Vish On May 2, 2011, at 4:34 PM, Eldar Nugaev wrote: Hi all. So what is the decision? I see three decisions: #1 Replace existed plain http to ssl #2 Add additional ports for ssl (save plain http) #3 Do nothing Eldar On Tue, Apr 26, 2011 at 11:27 AM, Dirk-Willem van Gulik dirk-willem.van.gu...@bbc.co.uk wrote: On 25 Apr 2011, at 19:47, Kirill Shileev wrote: Recently, playing with libcloud against a private openstack installation we realized that 8773 and 8774 ports listened by openstack-nova-api expect plain HTTP. This is something that is rarely allowed in production installations. . Other option would be making this configurable, although not sure why and where the plain HTTP might be justified. Any thoughts, comments? An important side effect of slapping SSL with client/server certs on pretty much all connection is that it makes all sort of governance and validation jobs much easier from an organisational point of view. With more 'reuse' of existing process and validation. The attack footprint/exposed estate now splits in three clean realms: issuing of client cert, security of the TCP and SSL layer - and a specific model for what happens within that connection. With the latter bound by the previous two. Furthermore client validation can be done with narly a secret in sight. So for those reasons alone - SSLis good. Dw. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eldar Skype: eldar.nugaev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Availability of RHEL build of Bexar release of OpenStack Nova
Hello! Grid Dynamics is proud to announce public availability of OpenStack Nova RHEL 6.0 build. At the moment we have RPMs for Bexar release. It was tested using KVM hypervisor on real hardware in multi-node mode. Here are instructions to install run our build: http://wiki.openstack.org/NovaInstall/RHEL6Notes Differences between usual setup and our build: - we have packages and dependencies (instead of installing nova manually in /usr/local/bla and doing easy_install for missing modules) - qcow2 support was enabled utilizing libguestfs instead of missing NBD - start-stop-daemon used as daemon management library due removed python-daemon module from Nova - Nova's logs are located in /var/log/nova and properly logrotated - network injection code was patched for RHEL path (/etc/sysconfig/network-scripts) and RHEL template - all dependencies are located in separate repository. Enjoy and please contribute all packaging bugs to me! All porting work are on GitHub: https://github.com/abrindeyev/openstack-nova-rhel6 Grid Dynamics Team: Andrey Brindeyev, Eldar Nugaev, Ilya Alekseyev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
