Re: [Openstack] How to deploy OpenStack on thousands of nodes?
I'd suggest to have a look at the openstack Operations Guide which contains information on scaling approaches (http://docs.openstack.org/ops/) In particular, the use of cells is a good way to build large scale infrastructures (see http://docs.openstack.org/trunk/openstack-ops/content/scaling.html) Tim smime.p7s Description: S/MIME cryptographic signature ___ 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] Trove implementation in Openstack with Red Hat 6
Michael, It is desirable that a project, such as Trove, in incubation would be able to install and run on Redhat derived systems as well as Ubuntu/Debian. With the combination of packstack/RDO, RedHat based deployment is becoming a lot easier and I would hope that this is considered to attract the maximum community and adoption by the early testers. Tim -Original Message- From: Openstack [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Michael Basnight Sent: 14 June 2013 17:30 To: cont...@andreagiardini.com Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Reddwarf implementation in Openstack with Red Hat 6 Hi Andrea, We currently have some compatibility issues wrt installing in rpm distros. I'm working on getting heat set up for our initial installation, and that will help alleviate some pain with the differing distros and how they install packages. I encourage you to set the system up in a Debian based system, like Ubuntu, to play around with it. As always, we are in #openstack-trove and I'd love to chat with you and try to help make the install/management a bit more pkg agnostic. I'm hub_cap in irc. Oh and ps, we changed our name to trove cuz of some not so well known tv series ;) Sent from my digital shackles On Jun 14, 2013, at 7:17 AM, cont...@andreagiardini.com wrote: Hi all, I'm trying to figure out how to install Reddwarf on a existing server running Openstack (installed trought RDO - http://openstack.redhat.com/) in a Red Hat 6 server. The actual script for Reddwarf seems to be Ubuntu-only and, obviously, nothing goes in the right way. Actually the script is also strictly connected with devstack ( http://devstack.org/ ) and using ./redstack post-devstack install doesn't work anyway. I tried to manually edit the scripts to make them Red Hat-compatible but I had a lot of issues for missing dependencies, outdated libraries, python versions, apt/yum repository etc... Did someone of you figured out how to make It work? Cheers Andrea ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] [ceilometer] support for older versions of ceilometer
Doug, Can you advise on what the plan/policy will be for Havana ? - Will I be able to run Havana core components such as Nova with Grizzly ceilometer ? - Will I be able to run Havana ceilometer with Grizzly core components (with reduced functionality compared to the Havana core components) ? Tim From: Openstack [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Doug Hellmann Sent: 30 May 2013 18:59 To: openstack@lists.launchpad.net Subject: [Openstack] [ceilometer] support for older versions of ceilometer The ceilometer team has had a few requests for help with older versions of ceilometer or running the grizzly version of ceilometer with older versions of other OpenStack components lately. We appreciate the level of interest in the project but, as much as we would like to, unfortunately we are not always able to help everyone with these mixed configurations. During the early phases of our development we tried to maintain compatibility with folsom, even well into the grizzly development cycle. We are no longer doing that, however, and so to make clear what support we can offer, the ceilometer team has put together the statement below. It has been added to our documentation, and we are posting here to make sure everyone has a chance to see it. Regards, Doug The ceilometer team has limited capacity to provide support for older versions of the project. Because the project graduated from incubation around the time of the grizzly release, that is the first version for which we will provide regular ongoing support following the standard deprecation cycle for OpenStack [1]. The grizzly version of ceilometer cannot be installed on the same server with earlier versions of OpenStack because of conflicting package requirements, but is API compatible with the folsom release if installed separately. [1] https://wiki.openstack.org/wiki/StableBranch smime.p7s Description: S/MIME cryptographic signature ___ 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] [ceilometer] support for older versions of ceilometer
The difficulties of upgrading OpenStack while running production services was one of the major feedbacks from the user survey at Portland. Core components are including N/N+1 upgrades into their plans for Havana so big bang (and high risk of extended downtime) upgrades are no longer the default processes. As a component matures through incubation to core, we also need to have these operational requirements covered. Upgrading 100s of hypervisors and their controllers require staged upgrades. I hope that ceilometer can also include this within the Havana timeframe as it becomes a key component of production, large scale clouds. Tim From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] Sent: 30 May 2013 22:35 To: Tim Bell Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [ceilometer] support for older versions of ceilometer From what I understand, it is unusual to support mixing components from different releases like that. Am I wrong? Doug On Thu, May 30, 2013 at 3:29 PM, Tim Bell tim.b...@cern.ch mailto:tim.b...@cern.ch wrote: Doug, Can you advise on what the plan/policy will be for Havana ? - Will I be able to run Havana core components such as Nova with Grizzly ceilometer ? - Will I be able to run Havana ceilometer with Grizzly core components (with reduced functionality compared to the Havana core components) ? Tim From: Openstack [mailto:openstack-bounces+tim.bell mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net mailto:cern...@lists.launchpad.net ] On Behalf Of Doug Hellmann Sent: 30 May 2013 18:59 To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Subject: [Openstack] [ceilometer] support for older versions of ceilometer The ceilometer team has had a few requests for help with older versions of ceilometer or running the grizzly version of ceilometer with older versions of other OpenStack components lately. We appreciate the level of interest in the project but, as much as we would like to, unfortunately we are not always able to help everyone with these mixed configurations. During the early phases of our development we tried to maintain compatibility with folsom, even well into the grizzly development cycle. We are no longer doing that, however, and so to make clear what support we can offer, the ceilometer team has put together the statement below. It has been added to our documentation, and we are posting here to make sure everyone has a chance to see it. Regards, Doug The ceilometer team has limited capacity to provide support for older versions of the project. Because the project graduated from incubation around the time of the grizzly release, that is the first version for which we will provide regular ongoing support following the standard deprecation cycle for OpenStack [1]. The grizzly version of ceilometer cannot be installed on the same server with earlier versions of OpenStack because of conflicting package requirements, but is API compatible with the folsom release if installed separately. [1] https://wiki.openstack.org/wiki/StableBranch smime.p7s Description: S/MIME cryptographic signature ___ 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] Dual network connections on hypervisor
I have a hypervisor running KVM with two network interfaces to two independent networks. I could not find any documentation on how to configure a set up such as this so the guests could also be configured with IPs on the two networks. Any pointers ? Tim smime.p7s Description: S/MIME cryptographic signature ___ 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] Share Glance between cells or regions
+2 I feel there is a difference between - Is it possible ? - Is it a good approach for use case X ? Multi-site varies hugely depending on whether the aim is sharing the work or recovery scenarios. Defining a good model for multi-site, resilient deployments and multi-site, maximum throughput/utilisation would be very interesting. Tim From: Openstack [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Narayan Desai Sent: 15 May 2013 21:14 To: John Paul Walters Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Share Glance between cells or regions +1. We're going to be running a bunch of parallel deployments of openstack for the purpose of experimentation in system design. it would be nice to be able to share glance and keystone between instances. -nld On Wed, May 15, 2013 at 1:46 PM, John Paul Walters jwalt...@isi.edu mailto:jwalt...@isi.edu wrote: Hi, We're looking at setting up a geographically distributed OpenStack installation, and we're considering either cells or regions. We'd like to share a single Glance install between our regions (or cells), so the same images can be spawned anywhere. From here: http://docs.openstack.org/trunk/openstack-ops/content/segregate_cloud.html it's not clear whether that's possible. Can anyone shed some light on this? Is it possible in regions OR cells (or both)? Is there a better solution that I'm not thinking of? thanks, JP ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Checkpoint VM and roll back
I'd like to be able to 1. checkpoint a running virtual machine 2. run a test 3. rollback to the checkpoint from step 1 Has anyone had experience of doing this using OpenStack (such as with snapshots) ? Tim smime.p7s Description: S/MIME cryptographic signature ___ 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] List of Cinder compatible devices
I think there will always be drivers which implement more features than others (in the same way as hypervisors). Thus, it should be easy for someone making choices on backend storage to determine to what extent a particular model is supported. There should also be a mechanism to evict a driver from the list in the event of failing to keep up with additional functionality (but this is a different question to the documentation). Tim From: Blair Bethwaite [mailto:blair.bethwa...@gmail.com] Sent: 16 April 2013 04:51 To: John Griffith; Tim Bell Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] List of Cinder compatible devices Hi John, Sounds sensible. I think this post kind of diverged from what Tim was asking, which seems to have been more about backend devices...? Should this page be removed then, and a summary of what you wrote added to the Cinder wiki page (including any exceptions for current core drivers)? (On a related note, I don't think List Snapshots should be there, IIUC that is not a function of the driver and rather about looking in the DB at data produced by create/delete snapshot driver calls.) Cheers, On 1 February 2013 04:12, John Griffith john.griff...@solidfire.com mailto:john.griff...@solidfire.com wrote: On Thu, Jan 31, 2013 at 8:56 AM, Koert van der Veer ko...@cloudvps.com mailto:ko...@cloudvps.com wrote: In that case, it is probably best to transpose the table, with series included, the number of products will yield too many columns to be workable. Also: Do blank spaces indicate not supported or unknown? koert On 01/31/2013 04:47 PM, Shake Chen wrote: I think need add Vendor storage series. like not all the EMC storage would support Cinder. On Thu, Jan 31, 2013 at 11:19 PM, Sébastien Han han.sebast...@gmail.com mailto:han.sebast...@gmail.com wrote: Just added some stuff about RBD where E refers to Essex. -- Regards, Sébastien Han. On Thu, Jan 31, 2013 at 11:20 AM, Avishay Traeger avis...@il.ibm.com mailto:avis...@il.ibm.com wrote: openstack-bounces+avishay=il.ibm@lists.launchpad.net mailto:il.ibm@lists.launchpad.net wrote on 01/31/2013 12:37:07 AM: From: Tom Fifield fifie...@unimelb.edu.au mailto:fifie...@unimelb.edu.au To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net , Date: 01/31/2013 12:38 AM Subject: Re: [Openstack] List of Cinder compatible devices Sent by: openstack-bounces+avishay=il.ibm@lists.launchpad.net mailto:il.ibm@lists.launchpad.net Here's a starting point: http://wiki.openstack.org/CinderSupportMatrix Regards, Tom Tom, Thanks for doing this. I recommend that instead of Y, we should put the letter of the version in which the feature first appeared. So for example, E, F, G, ... Thanks, Avishay ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- Shake Chen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto: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 mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp So thanks for putting this together but this brings something up that I've been meaning to raise on the dev-list anyway. In my opinion it should be a requirement that for a driver to be accepted in Cinder it implements all of the functionality of the base LVM driver (ie all of the rows listed in the matrix here). Having to go through and determine what feature is or is not supported per driver is EXACTLY what I want to avoid. If we go down the path of building a matrix and allowing partial integration it's going to create a huge mess and IMO the user experience is going to suffer greatly. Of course a driver can do more than what's on the list, but I think this is the minimum requirement and I've been pushing back on submissions based on this. The only exceptions have been some of the newer Grizzly features, but that's only because we're
Re: [Openstack] Project quotas on multi-region
The Boson project was looking at this sort of problem (https://wiki.openstack.org/wiki/Boson). There is a session at the summit to review this and other activities since it appears quotas are appearing in many projects and there is a clear need for multi-cell and quota delegation (i.e. domain quota manager gives sub-sections to project quota managers). This sort of function is quite complex to implement and consistency of implementation would be strongly desirable. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Nathanael Burton Sent: 24 March 2013 02:31 To: Aguiar, Glaucimar (Brazil RD-ECL) Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net Subject: Re: [Openstack] Project quotas on multi-region On Mar 23, 2013 7:59 PM, Aguiar, Glaucimar (Brazil RD-ECL) glaucimar.agu...@hp.com mailto:glaucimar.agu...@hp.com wrote: Hi, In a deployment scenario where one keystone has several regions registered, how the project quota are managed by, as an example, two nova services in two different regions? I am wondering if is it possible to set quota on the project for all regions or this must to be done on a region by region basis which really means a quota for a project in a region. Thanks in advance, Glaucimar Aguiar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Glaucimar, Currently quotas are maintained within each nova system so there is not a global view/management/enforcement of quotas. I would love to see a discussion of centralizing things from nova like key pairs, AZs, and quotas in keystone. Thanks, Nate smime.p7s Description: S/MIME cryptographic signature ___ 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] Name restrictions and other checks
We have some additional checks on the names of instances such as - Maximum length (to be compatible with Active Directory) - Restrict characters which are usable Is there a configurable set of parameters for these checks (or a user exit to define a functional check) ? If there is not something like this, are there examples of similar exits which we could model a patch on ? Tin smime.p7s Description: S/MIME cryptographic signature ___ 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] Unauthenticated service probe for OpenStack components
Is there a method to do a basic service status check for OpenStack components ? I'd like to able to validate that the daemons are able to handle an unauthenticated request from a monitoring script. This is somewhat equivalent to a network level ping or nagios probe, i.e. validate that there is something on the other end of the pipe. I want to avoid having to handle credentials if possible (so running image-list is not an option) Currently, curl to the service URL just gives 401 error. Any ideas ? Tim smime.p7s Description: S/MIME cryptographic signature ___ 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] List of Cinder compatible devices
Is there a list of devices which are currently compatible with cinder and their relative functionality ? Looking through the source code, there are EMC, IBM, NetApp, Nexenta but it is not clear which models are supported or if there are other products also. A functionality matrix (like there is for hypervisors in Nova) would be very useful. Tim smime.p7s Description: S/MIME cryptographic signature ___ 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] Name
There is also Robin Hood (http://en.wikipedia.org/wiki/Robin_hood) steal from the rich and give to the poor Personally, Havana got my vote . Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Matt Joyce Sent: 24 January 2013 20:58 To: Marton Kiss Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Name it Hood! Don't forget the HMS hood who was sunk by the Bismark. Rallying the British navy to seek vengeance and crush the unsinkable foe. =P -Matt On Thu, Jan 24, 2013 at 11:53 AM, Marton Kiss marton.k...@gmail.com mailto:marton.k...@gmail.com wrote: And it also means beaver in hungarian. :) http://translate.google.hu/?hl=en http://translate.google.hu/?hl=entab=wT#en/hu/beaver tab=wT#en/hu/beaver Márton 2013/1/24 Monty Taylor mord...@inaugust.com mailto:mord...@inaugust.com Hey all! Here's my pitch for Hood: a) It's the tallest mountain in Oregon, and honestly, it's a pretty kick-ass mountain in general b) Being in the pacific northwest, the mountain itself is quite regularly in the clouds. That's gotta count for something. c) It's actually a volcano. d) Mount Hood is CLEARLY an Oregon thing. Havana is clearly a town in Cuba. (We should have a design summit in cuba!!!) e) Harbor is super-problematic because of the US/UK clash in spelling. Half of us will spell it wrong no matter what. f) Hood is only 4 letters. Think about that when you think about typing hatfield a lot. Also, if we name it hatfield, we're going to have to have the M summit somewhere that has a town called McCoy. g) I'll buy you a beer at the summit if you vote for Hood. Monty ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto: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 mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Windows instance licensing in OpenStack
Sounds like activation key management would be a great feature for the Windows cloud-init so this could be passed in as meta data. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Balamurugan V G Sent: 23 January 2013 18:12 To: Peter Pouliot Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Windows instance licensing in OpenStack Thanks for the inputs everyone. My concern is if the activation/licence key input needs to be done on each VM after they boot up or its just as simple as having as many licences as the VMs before hand and nothing needs to be done after the instance boots up. Regards, Balu On Wed, Jan 23, 2013 at 10:31 PM, Peter Pouliot ppoul...@microsoft.com mailto:ppoul...@microsoft.com wrote: Ok, I am no MS licensing expert, however. Here is my understanding of it. If you are using a windows vm on a hypervisor other than windows server with the Hyper-V role enabled you need to license per vm. If you are using windows server with Hyper-V enable you can license at the hypervisor/server rather than at the vm level. This does not include Hyper-V server, which only requires licensing of the windows guests. p Peter J. Pouliot, CISSP Senior SDET, OpenStack Microsoft New England Research Development Center One Memorial Drive,Cambridge, MA 02142 ppoul...@microsoft.com mailto:ppoul...@microsoft.com | Tel: +1(857) 453 6436 -Original Message- From: openstack-bounces+ppouliot=microsoft@lists.launchpad.net mailto:microsoft@lists.launchpad.net [mailto:openstack-bounces+ppouliot mailto:openstack-bounces%2Bppouliot =microsoft@lists.launchpad.net mailto:microsoft@lists.launchpad.net ] On Behalf Of Jay Pipes Sent: Wednesday, January 23, 2013 9:31 AM To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Windows instance licensing in OpenStack On 01/23/2013 08:41 AM, Balamurugan V G wrote: Hi, I wonder how the Windows Licensing would work in OpenStack. Lets say I have a Windows Image which I have already activated. Now if I launch N instances of this image, what are the SO licensing implications? Will I have to license/re-activate on each of the instances after they boot up? If you use XenServer or KVM, I believe so, yes. I've heard that if you use ESXi you can get some sort of license for all Windows images on a host. Not sure of the details of this, though, I've just heard it through the IT grapevine... Best, -jay p.s. If you find out any more solid info, please do post back :) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto: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 mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] using Win AD authentication as keystone backend
We run Active Directory with Keystone at CERN. The configuration is documented by Jose in the Wiki at http://wiki.openstack.org/HowtoIntegrateKeystonewithAD. Not sure if all the patches made it into Folsom though. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Liu Wenmao Sent: 22 January 2013 04:23 To: openstack@lists.launchpad.net Subject: [Openstack] using Win AD authentication as keystone backend hello all: My company use Windows AD(active directory) authentication for internal user login, is it possible to integrate the current authentication with keystone backend, so that we do not extra user/password maintaining. Hope Openstack Folsom has an easy and stable solution. thanks Wenmao Liu NSFOCUS smime.p7s Description: S/MIME cryptographic signature ___ 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] user committee points to review
A few of you have had trouble reading the document. The updated link is at https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqET oyo/edit If you can't read it, please send me a note and I'll share it. Tim From: Tim Bell Sent: 09 January 2013 09:52 To: 'Sean Roberts'; OpenStack community; openstack Subject: RE: Calling all user group and meetup organizers Sean, Is the aim to provide co-ordination for the OpenStack user groups worldwide ? Ryan, JC and I have been putting together the structure for the OpenStack user committee (as described on the foundation list at http://lists.openstack.org/pipermail/foundation/2012-December/001289.html). As we have collected input from various parties, there is a proposal for part of the committee to consist of user group representatives from different geographies. As mentioned in the mail to the foundation list, anyone who'd like to contribute to the user committee structure/mandate is welcome to get in touch for editing rights to https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqET oyo I am on travel on the 15th so I won't be able to attend the call but it would be great if the conclusions could be distributed to the community list. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Sean Roberts Sent: 09 January 2013 01:55 To: OpenStack community; openstack Subject: [Openstack] Calling all user group and meetup organizers We are going to have a planning meeting on Tuesday, 15 Jan 2012 11:00am to 1:00pm PST. RSVP via http://www.meetup.com/openstack/events/93593062 http://www.meetup.com/openstack/events/93593062/ Connect remotely via webex https://yahoomeetings.webex.com/yahoomeetings/j.php?ED=160663792UID=492396 097RT=MiM0 https://yahoomeetings.webex.com/yahoomeetings/j.php?ED=160663792UID=4923960 97RT=MiM0 If this time doesn't work for you, get ahold of me directly via skype:seanroberts66, email, mobile, irc:sarob, twitter:sarob, or carrier pigeon. Stefano and Thierry will be joining us. I want to get input from people that run user groups and meetups. See you then! Sean Roberts Infrastructure Strategy mailto:sean...@yahoo-inc.com sean...@yahoo-inc.com Direct (408) 349-5234 Mobile (925) 980-4729 701 First Avenue, Sunnyvale, CA, 94089-0703, US Phone (408) 349-3300 Fax (408) 349-3301 http://forgood.zenfs.com/logos/yahoo.png smime.p7s Description: S/MIME cryptographic signature ___ 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] Migrate Instance to another Tenant ID in the same environment
Updating the DB for the project would be one step but there are other potential things to consider such as attached volumes. Building up the set of things that need to be done in the doc would be useful but eventually we need to get to an openstack command that can do this (or do the equivalent clone/snapshot function which may be more generic for other use cases such as replicating a VM/volumes for testing) Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Davide Guerri Sent: 10 January 2013 11:23 To: Alex Vitola Cc: L - OpenStack Subject: Re: [Openstack] Migrate Instance to another Tenant ID in the same environment Thanks for this one. ... someone should really maintain a wiki with all the tricks that are passing through this ML! Cheers, Davide. On 10/gen/2013, at 11:15, Alex Vitola alex.vit...@gmail.com wrote: Changed directly by the database. Not the best way but I did because it was an environment. So far I have not found any problems mysql use nova; mysql UPDATE `nova`.`instances` SET `user_id` = 'c892202c2a134b8e9f19c047f29c60ee', `project_id` = 'debd50b4ec2b4905a3296ac0f0971849' WHERE `instances`.`id` =7; att Alex Vitola 2013/1/10 Razique Mahroua razique.mahr...@gmail.com +1 Seb, have you ever tried to change the tenant id for an instance into the database and reboot/ recover it? I wonder how nova behaves into such case Razique Mahroua - Nuage Co razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 Le 9 janv. 2013 à 22:18, Sébastien Han han.sebast...@gmail.com a écrit : Moving instances from project to project is not possible however what you can do is (safe way): - as an admin user - snapshot the image from env 1 - grab the snapshotted file from your glance store - import the snapshot into glance - make the image public - run the snapshot from env 2 - enjoy! Cheers! -- Regards, Sébastien Han. On Wed, Jan 9, 2013 at 8:14 PM, Alex Vitola alex.vit...@gmail.com wrote: I have 2 projects in my environment: ProjectQA1: ID - 0001 ProjectQA2: ID - 0002 root@Controller:# keystone tenant-list +-++-+ | id |name| enabled | +-++-+ | 0001| ProjectQA1 | True | | 0002| ProjectQA2 | True | +--++-+ In Project 1 there are 1 instance In Project 2 there are 7 instances root@Controller:# nova usage-list +---+---+--+---+---+ | Tenant ID | Instances | RAM MB-Hours | CPU Hours | Disk GB-Hours | +---+---+--+---+---+ | 0001 | 1 | 12533.78 | 24.48 | 244.80| | 0002 | 7 | 127447.40| 171.17| 2100.45 | +---+---+--+---+---+ Is it possible to move this instance of Project 1 for 2? root@Controller:# nova list +--+---+++ | ID | Name | Status | Networks | +--+---+++ | 9991 | QA-07 | ACTICE | Net-Demo=200.100.50.25 | +--+---+++ Move ID 9991/QA-07 from: Tenant ID 0001 to: Tenant ID 0002 Is that possible? Att Alex Vitola System Administrator ___ 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Calling all user group and meetup organizers
Sean, Is the aim to provide co-ordination for the OpenStack user groups worldwide ? Ryan, JC and I have been putting together the structure for the OpenStack user committee (as described on the foundation list at http://lists.openstack.org/pipermail/foundation/2012-December/001289.html). As we have collected input from various parties, there is a proposal for part of the committee to consist of user group representatives from different geographies. As mentioned in the mail to the foundation list, anyone who'd like to contribute to the user committee structure/mandate is welcome to get in touch for editing rights to https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqET oyo I am on travel on the 15th so I won't be able to attend the call but it would be great if the conclusions could be distributed to the community list. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Sean Roberts Sent: 09 January 2013 01:55 To: OpenStack community; openstack Subject: [Openstack] Calling all user group and meetup organizers We are going to have a planning meeting on Tuesday, 15 Jan 2012 11:00am to 1:00pm PST. RSVP via http://www.meetup.com/openstack/events/93593062 http://www.meetup.com/openstack/events/93593062/ Connect remotely via webex https://yahoomeetings.webex.com/yahoomeetings/j.php?ED=160663792UID=492396 097RT=MiM0 https://yahoomeetings.webex.com/yahoomeetings/j.php?ED=160663792UID=4923960 97RT=MiM0 If this time doesn't work for you, get ahold of me directly via skype:seanroberts66, email, mobile, irc:sarob, twitter:sarob, or carrier pigeon. Stefano and Thierry will be joining us. I want to get input from people that run user groups and meetups. See you then! Sean Roberts Infrastructure Strategy mailto:sean...@yahoo-inc.com sean...@yahoo-inc.com Direct (408) 349-5234 Mobile (925) 980-4729 701 First Avenue, Sunnyvale, CA, 94089-0703, US Phone (408) 349-3300 Fax (408) 349-3301 http://forgood.zenfs.com/logos/yahoo.png smime.p7s Description: S/MIME cryptographic signature ___ 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] How to deploy openstack automatically in your env.
Lei, At CERN, we run our RHEL-based OpenStack instance with the puppetlabs modules. They work very well and simplify the multi-node deployments. We've got around 200 hypervisors deployed with this method. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Derek Higgins Sent: 03 December 2012 16:37 To: Lei Zhang Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] How to deploy openstack automatically in your env. Hi Lei, On 12/03/2012 09:15 AM, Lei Zhang wrote: Hi all, I search the internet for days and found several automatically tool. Including * devstack * puppet+pupet-openstack * stackops * OneStack But It seems that all the scripts are well tested on ubuntu not RHEL. How could you guys to deploy the openstack automatically, especially on RHEL. a lot of work has gone into the puppetlabs puppet modules so that they work on RHEL, you can download the modules from their github account https://github.com/puppetlabs/ alternatively, I have been working on a tool to deploy openstack on RHEL and Fedora, its still at early stages and probably a bit rough around the edges but if your interested you can try it out https://github.com/fedora- openstack/packstack currently you can use packstack to install folsom keystone, glance, nova, cinder, horizon and swift on Multiple RHEL or Fedora servers. If you want to try it out it would be great to get any feedback you have. packstack uses the puppetlabs modules to apply puppet manifests to individual servers without the requirement of having a puppet master server. thanks, Derek. -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] Is there any way to migrate the Instance between the projects/tenants?
We were also interested in this function but could not find an easy way to do it. The operation becomes more complex when there are attached volumes and potentially different permissions between the two projects. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Lei Zhang Sent: 29 November 2012 06:09 To: openstack@lists.launchpad.net Subject: [Openstack] Is there any way to migrate the Instance between the projects/tenants? Hi all, As the subject say, is there any way to do this? I search the Internet and only found the migration bewteen two physical machine. thanks -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l smime.p7s Description: S/MIME cryptographic signature ___ 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] [ceilometer] Monitoring physical devices
There is a use case for base metal hardware metering in the private cloud where the user allocated the machine does not have root access to kill the metering. Being able to create a single metering infrastructure for the entire private cloud, virtual or bare-metal allocation, is a need technically, it is not clear how to guarantee it but it is worth exploring. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Robert Collins Sent: 06 November 2012 11:00 To: Graf Lucas (graflu0); Zehnder Toni (zehndton); openstack@lists.launchpad.net; Doug Hellmann Subject: Re: [Openstack] [ceilometer] Monitoring physical devices On Tue, Nov 6, 2012 at 10:53 PM, Julien Danjou jul...@danjou.info wrote: On Tue, Nov 06 2012, Graf Lucas (graflu0) wrote: I'm a little confused now... ;) Is the bare metal run by the platform operator the physical machine? What do you mean with the bare metal run to replace virtual instances for any project? AFAIU, bare-metal provisionning is about using hardware (bare-metal) rather than virtual instances as a flavor in Nova. For such case, we won't be able to poll anything about the hardware. For hardware ran by the operator, this will be doable. We can still talk to the IPMI controller for the machine, which will get us lots of info, without running agents in the host os. -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Is there any method to Activate Windows during Launch a new Instance?
Have you had a look at cloud-init ? Tim - Reply message - From: Ray Sun qsun01...@cienet.com.cn To: openstack openstack@lists.launchpad.net Subject: [Openstack] Is there any method to Activate Windows during Launch a new Instance? Date: Sat, Nov 3, 2012 03:04 I create a windows 7 image(without activate) and upload to glance, and I can successfully start it up. But how can I automatically activate it after user launch it? Or how can I inject the SN into windows during startup? Or any other better idea? Thanks a lot. - Ray Yours faithfully, Kind regards. CIeNET Technologies (Beijing) Co., Ltd Email: qsun01...@cienet.com.cnmailto:qsun01...@cienet.com.cn Office Phone: +86-01081470088-7079 Mobile Phone: +86-13581988291 ___ 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] Distributed configuration database
Puppet is great for this sort of thing. There are various ways of querying parameters and making choices about them. A typical example would be where you want to adjust a configuration parameter due to memory configuration or network. Writing the puppet configuration is not difficult... Puppetlabs have an excellent and actively maintained configuration suite on the puppetforge for OpenStack along with tutorial videos. Chef support is also there so there is choice. The DevOps panel gives some discussion around this (http://www.openstack.org/summit/san-diego-2012/openstack-summit-sessions/pr esentation/devops-panel) I think building an openstack specific database for configuration would be hard work to include all of the flexibility that Puppet offers. It is worth having a good look at puppet or chef before starting this. Tim @Jon - I am happy that these ideas resonate with you. My moot point is that the metadata should be within the openstack implementation and not outside. I am not very familiar with Puppet - is there a way to query the parameters set in the conf file. I would think that Puppet would be given a conf file to deploy. The values within the conf file would still remain abstracted and not be readily available. Please correct me if I'm wrong in my presumption. Having the parameters with their default values in the data store would allow a better understanding of the different configuration parameters. Also if its in a database then dependency and relationship rules or even constraints (permissible values) could be defined. smime.p7s Description: S/MIME cryptographic signature ___ 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] Quotas in folsom
+1 for Boson ... this is a key area for CERN too. When you have a fixed budget and no credit cards, quota management is a strong requirement! Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Kevin L. Mitchell Sent: 29 October 2012 20:26 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Quotas in folsom On Mon, 2012-10-29 at 18:01 +, Gabriel Hurley wrote: It's also worth noting that we are now in territory where quotas are controlled by multiple projects: volumes and gigabytes have quotas in both Nova and Cinder; network quotas are in both Nova and Quantum... While I don't think it makes sense to try and centralize these things, I think the projects could coordinate more to understand who should be managing a given quota and to try and make the end-user experience less baffling. It's also worth noting that I've finally been able to start working on Boson, which may help with that… -- Kevin L. Mitchell kevin.mitch...@rackspace.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 smime.p7s Description: S/MIME cryptographic signature ___ 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] Use of MAC addresses in Openstack VMs
If we purchase an OUI, is there a mechanism within Quantum to only allocate Mac addresses with that prefix ? Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Salvatore Orlando Sent: 20 October 2012 10:20 To: Vinay Bannai Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Use of MAC addresses in Openstack VMs Hi Vinay, I understand your concerns about conflicts with already assigned OUIs. It is however my opinion that it is not up to the Openstack Foundation, but to entities deploying Openstack, to buy MAC OUIs. As regards Quantum, we should ensure the default MAC range we use is locally assigned; unfortunately I do not know enough about nova-network. Also, it is my opinion that a locally-assigned OUI would be sufficient for many use cases, without the need for a globally assigned one. Regards, Salvatore On 20 October 2012 04:05, Vinay Bannai vban...@gmail.com wrote: I was talking to Nachi and Gary during the Quantum design session about the need to have a proper MAC OUI allocation scheme for Openstack development folks. They suggested that I send it out for wider discussion on the mailing list. It turns out that it would be useful for the Openstack foundation to apply for a MAC OUI from IEEE that can be used for development purposes and testing. This way we don't unwittingly use someone else MAC allocation. Here are the details http://standards.ieee.org/develop/regauth/oui/index.html http://standards.ieee.org/develop/regauth/oui/index.html The cost to get a OUI allocation is around $2000 dollars. Remember if we use random MAC OUI, the actual owners can assert their legal claim on the MAC address in the event of a conflict now that we have support for more sophisticated tunnels that allow connections from public and private clouds. Comments welcome. Vinay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] File Injection through Horizon
Cloud-init is also available on RHEL systems too. We're using it extensively to contextualise VMs on Scientific Linux. We've even tried a windows version but this is not as functional. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Kiall Mac Innes Sent: 03 October 2012 14:13 To: Srikanth Kumar Lingala Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] File Injection through Horizon Hi Srikanth, File Injection is not available through Horizon. Atul is describing a different feature that can be used to achieve similar results. The contents of User-Data will be accessible to the instance via http://169.254.169.254/latest/user-data; - Ubuntu ships with a tool called cloud-init that makes use of this data if available. Eg One of the simple use cases for cloud-init is, if the data starts with #!, it will assume it's a shell script and download + execute it. This can, in a roundabout way, be used to achieve similar results to the file injection feature. Thanks, Kiall On Wed, Oct 3, 2012 at 12:59 PM, Srikanth Kumar Lingala srikanthkumar.ling...@gmail.com wrote: Hi, I am able to create an instance with the following command (along with File Injection): # nova boot --file /root/inject.txt=/root/inject.txt --flavor=1 --image=4671e99b-1c01-42e8-94d6-2405a59bab57 testserver1 Now, what I need is to do the same from the Horizon. I will select a file to inject from Horizon and Launch the Instance, it should inject that file. Regards, Srikanth. On Wed, Oct 3, 2012 at 4:18 PM, Atul Jha atul@csscorp.com wrote: Hi, The test step followed for user-data as follows. 1. Got image from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-i386- disk1.img 2. Booted it from Horizon and passed the script in the file #!/bin/sh mkdir /home/ubuntu/testdir 3. Logged in to the machine with ssh -i mykey.pub ubuntu@IP And i can see the directory created. File injection via Horizon uses cloud-init and i have tested it on Ubuntu 12.04 i have no idea about other distributions. You can file more about cloud-init here :- https://help.ubuntu.com/community/CloudInit And thanks, i will add this in the doc somewhere. :) Hope it helps. Atul jha From: Shake Chen [shake.c...@gmail.com] Sent: Wednesday, October 03, 2012 2:28 PM To: Srikanth Kumar Lingala Cc: Atul Jha; openstack@lists.launchpad.net Subject: Re: [Openstack] File Injection through Horizon I also have same question. can you give us example. how to injection throuth Horizon? On Wed, Oct 3, 2012 at 3:24 PM, Srikanth Kumar Lingala srikanthkumar.ling...@gmail.commailto:srikanthkumar.ling...@gmail.com wrote: Hi Atul, Can you please guide me how to do File Injection through Horizon? Regards, Srikanth. On Wed, Oct 3, 2012 at 12:41 PM, Atul Jha atul@csscorp.commailto:atul@csscorp.com wrote: Hi, snip I have some doubts regarding File Injection. Can File Injection can be done through Horizon, while creating an Instance? While creating an Instance from Horizon, a field called 'User Data' [text area] is there. Is that field is related to File Injection? Can anyone tell me, the values we need to give for 'User Data'? /snip Yes. Cheers!! Atul Jha http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Shake Chen http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] File Injection through Horizon
Yes, we're running the RHEL EPEL and the Fedora one. The source is marked as http://launchpad.net/cloud-init rpm -qi cloud-init-0.6.3-0.5.bzr532.fc17.noarch Name: cloud-init Version : 0.6.3 Release : 0.5.bzr532.fc17 Architecture: noarch Install Date: Tue 02 Oct 2012 12:31:18 PM CEST Group : System Environment/Base Size: 477568 License : GPLv3 Signature : RSA/SHA256, Mon 17 Sep 2012 12:01:39 AM CEST, Key ID 50e94c991aca3465 Source RPM : cloud-init-0.6.3-0.5.bzr532.fc17.src.rpm Build Date : Fri 14 Sep 2012 06:57:21 AM CEST Build Host : buildvm-15.phx2.fedoraproject.org Relocations : (not relocatable) Packager: Fedora Project Vendor : Fedora Project URL : http://launchpad.net/cloud-init Summary : Cloud instance init scripts Description : Cloud-init is a set of init scripts for cloud instances. Cloud instances need special scripts to run during initialization to retrieve and install ssh keys and to let the user run various scripts. Tim -Original Message- From: Blair Bethwaite [mailto:blair.bethwa...@gmail.com] Sent: 03 October 2012 14:39 To: Kiall Mac Innes Cc: Tim Bell; openstack@lists.launchpad.net Subject: Re: [Openstack] File Injection through Horizon On 3 October 2012 22:35, Kiall Mac Innes ki...@managedit.ie wrote: Ah - I had meant the RHEL version :) That'd be why you explicitly mentioned Debian-isms! Nothing to see here... -- Cheers, ~Blairo smime.p7s Description: S/MIME cryptographic signature ___ 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] CY12-Q3 Community Analysis — OpenStack vs OpenNebula vs Eucalyptus vs CloudStack
Were the developer and operator lists included in your analysis ? - http://lists.openstack.org/pipermail/openstack-dev/ - http://lists.openstack.org/pipermail/openstack-operators/ Full set is at http://wiki.openstack.org/MailingLists Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Qingye Jiang (John) Sent: 02 October 2012 08:37 To: openstack@lists.launchpad.net Subject: [Openstack] CY12-Q3 Community Analysis - OpenStack vs OpenNebula vs Eucalyptus vs CloudStack Hi, I have just finished my blog entry CY12-Q3 Community Analysis - OpenStack vs OpenNebula vs Eucalyptus vs CloudStack, which provides a lot of details on how these four projects are doing in terms of community activies. The article contains a lot of graphs, and I don't want to spam everybody's mailbox. It is accessible from my blog at the following URL: http://www.qyjohn.net/?p=2427 Best regards, Qingye Jiang (John) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] OpenStack and HyperV
I am not sure if I understand your question but Microsoft are making substantial contributions towards OpenStack such as the work on Hyper-V. The meeting logs are http://www.gossamer-threads.com/lists/openstack/dev/17175. Peter Pouliot could give more details. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Frans Thamura Sent: 15 September 2012 01:07 To: openstack@lists.launchpad.net Subject: [Openstack] OpenStack and HyperV hi all do u have slide regarding OpenSTack and HyperV or anything related to Microsoft i tought Microsoft activate again the OpenStack team in Europe, CMIIW can get more information for this? MS OpenSource Relation in this country ask this F smime.p7s Description: S/MIME cryptographic signature ___ 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] Quantum -. Multi-Plugin and support for provisioning of other devices.
There has been some load balancing discussion and more is due at the summit. The various current activities are summarised in http://wiki.openstack.org/Quantum/LBaaS Can you explain what you mean by storage devices with respect to Quantum ? The storage activities are underway as part of Cinder. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Endre Karlson Sent: 09 September 2012 19:57 To: openstack@lists.launchpad.net Subject: [Openstack] Quantum -. Multi-Plugin and support for provisioning of other devices. Hi, I am wondering if there are any community plans to support to use Quantum to provision up interfaces on other devices in areas of say LoadBalancers, Storage devices etc and if there are plans to support multi-active plugins in Quantum for this? Is there a timeframe maybe? Endre. smime.p7s Description: S/MIME cryptographic signature ___ 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] Quantum PTL election - please check Voters list
Can we integrate the registration process for the CLA with that of the membership ? There is likely to be some additional questions such as affiliation and interest in OpenStack, so it cannot be automatic but I would hope that most contributors to the code base would also be interested in other areas of governance also if we make it lightweight enough. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Duncan McGreggor Sent: 06 September 2012 19:12 To: Dan Wendlandt Cc: Thierry Carrez; openstack@lists.launchpad.net Subject: Re: [Openstack] Quantum PTL election - please check Voters list On Thu, Sep 6, 2012 at 9:03 AM, Dan Wendlandt d...@nicira.com wrote: I must admit even I was unaware of the requirement to be a individual foundation member in order to vote in PTL elections (I personally happen to be a member already). There are definitely at least a few people on the list below that I feel should be able to vote but can't, including two core members, Sumit and Aaron. The summary for the elections process that I saw sent to the list (see below) said nothing about foundation membership, and said that the process is mostly the same used in past PTL/PPB elections, which clearly did not have a foundation requirement because the foundation didn't exist. This is not the end of the world, but I'm guessing both Gary and I would both feel better if people had a chance to revisit their foundation status. Is there anything we can do about this? I hope so! I'm still reading this thread, but I've recommended that we give ATCs a chance to register as Foundation members now, and then accept them as valid voters... d ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Migration
I think a new release should contains details of how to do the upgrade (rather than discovering as we try it) I should aim that the deliverables for each of the projects in a new version includes in the release notes: A. dependencies (i.e. does glance folsom need to talk to horizon folsom or can it also talk to horizon essex) B. migration steps to move an instance to the latest version (i.e. how do I get glance essex to glance horizon) Planning an production upgrade will be very time consuming if it requires the person(s) to understand all the components in depth and derive the steps from the bug fixes. One of the items to review within the user/project feedback loop would be how we validate for a release (I used to call this system test as opposed to integration test, years ago). This would be the steps where we validate that a release complies with a set of deployability criteria (such as migration steps and documentation). Would the upcoming Folsom release meet these criteria (A./B.) for each core project ? Tim It would be fascinating (for me at least :)) to know the upgrade process you use - how many stages you use, do you have multiple regions and use one/some as canaries? Does the downtime required to do an upgrade affect you? Do you run skewed versions (e.g. folsom nova, essex glance) or do you do lock-step upgrades of all the components? For Launchpad we've been moving more and more to a model of permitting temporary skew so that we can do rolling upgrades of the component services. That seems in-principle doable here - and could make it easier to smoothly transition between versions, at the cost of a (small) amount of attention to detail while writing changes to the various apis. -Rob ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] User Friendly Development
I worry that if the users meet just a day before the conference, we cannot consolidate the input. Having the time to work out that a large share of the users are blocked on a specific problem is an important input to the conference. A single user may have specific problems to be addressed but if these are shared by many others, the community needs to listen. There is also a clarification required of what a 'user' is … cloud partners are both users and developers …. many people involved in the community have different hats with more/less engineering resource and more/less production deployment experience. I'm happy to help to consolidate the current pain points. We should gather the data for both Diablo and Essex based deployments and it may well be that many of them are addressed in Folsom (but we should check to be sure). Tim Bell CERN On 27 Jul 2012, at 19:38, Vishvananda Ishaya wrote: On Jul 27, 2012, at 10:18 AM, Mark Collier wrote: I do wonder if it would make sense to gather user feedback and goals before the summit, like the day (or week) before, to help provide some priorities (from their perspective) to consider going into the summit. This does seem valuable, although keep in mind that most users are a release behind, so the majority of their feedback will hopefully have been handled already :) Vish ___ 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
Re: [Openstack] Identity API v3 - Why allow multi-tenant users?
I thought that the v3 API supports domains as a group of tenants which would make the question rather different. Thus, I guess the question is A. Should there be users in multiple tenants in a single domain ? B. Should there be users in multiple domains ? There are clear use cases for A (such as researchers working on multiple projects sharing project quotas) For B, it is less clear as if I am a domain administrator, I do not want to be told that I cannot allocate user X since another domain has already taken it. On the other hand, there is a clear architectural benefit from having the concept of identity (and authentication) split off from roles and projects. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of John Postlethwait Sent: 18 July 2012 07:42 To: Rouault, Jason (Cloud Services) Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? Forcing a user to remember different usernames and/or passwords for each project they are a part of, when it is possible they are part of N projects, really isn't an acceptable option in my opinion. I believe that regardless of the engineering complexities, the end users shouldn't have to feel pain in order to make engineering the solutions and features they interact with easier. Software is for end users (in their various forms) and as such we need to take that into account when we make decisions. While no functionality is lost per se, there is a major end-user impact, and that should be reason enough to implement it… John Postlethwait Nebula, Inc. 206-999-4492 On Tuesday, July 17, 2012 at 4:15 PM, Rouault, Jason (Cloud Services) wrote: One benefit is the user does not need to have multiple sets of credentials to interact with multiple projects. Jason From: openstack-bounces+jason.rouault=hp@lists.launchpad.net [mailto:openstack-bounces+jason.rouault=hp@lists.launchpad.net] On Behalf Of Adam Young Sent: Tuesday, July 17, 2012 11:55 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? On 05/29/2012 01:18 PM, Caitlin Bestler wrote: One of the major complication I see in the API is that users can be associated with multiple tenants. What is the benefit of this? What functionality would be lost if a human user merely had to use a different account with each tenant? There are numerous issues with multi-tenant users. For example, if a user is associated with multiple tenants, who resets the user’s password? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Did you ever get an answer? This has been discussed in depth. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Identity API v3 - Why allow multi-tenant users?
Thanks.. My worry is the username. Currently, I have OS_USERNAME=timbell Not OS_USERNAME=timb...@cern.ch Does that mean in the future that my OS_USERNAME=timbell OS_DOMAINNAME=cern.ch I would like that I could still register as timbell in my domain even if someone else on the same OpenStack instance has a user id of timbell. Cross domain, federated identity as part of an authorization layer would be an interesting development (as we look to federated clouds and bursting) but I didn't see something like that in v3. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Adam Young Sent: 18 July 2012 17:46 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? The idea of a Domain is that it is a single administrative entity, such as a company. When a person joins a company, they get an email adddress. THat address does not change regardless of the position they hold. Tenants are administrative groupings below that. It is unfortunate that we used the name tenants for this, as it actually contradicts the usual meaning of the term. We will be shortly switching back to using the term projects, and I think that is clearer. It certainly makes sense for a user to belong to one domain, but have access to a project controlled in another domain. Here is a scenario. Joe's Sporting Goods and Local Bank are both companies that have a presense in a coud provider. Each has their own domain. t...@localbank.com is going to set up a Point of Sale system for Joe. So Joe creates a project called joes-point-of-sale and provides access to user t...@localbank.com. On 07/18/2012 02:46 AM, Matt Joyce wrote: I could see service users and security / operations teams having a need to span many domains. -Matt On Tue, Jul 17, 2012 at 11:24 PM, Tim Bell tim.b...@cern.ch wrote: I thought that the v3 API supports domains as a group of tenants which would make the question rather different. Thus, I guess the question is A. Should there be users in multiple tenants in a single domain ? B. Should there be users in multiple domains ? There are clear use cases for A (such as researchers working on multiple projects sharing project quotas) For B, it is less clear as if I am a domain administrator, I do not want to be told that I cannot allocate user X since another domain has already taken it. On the other hand, there is a clear architectural benefit from having the concept of identity (and authentication) split off from roles and projects. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net] On Behalf Of John Postlethwait Sent: 18 July 2012 07:42 To: Rouault, Jason (Cloud Services) Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? Forcing a user to remember different usernames and/or passwords for each project they are a part of, when it is possible they are part of N projects, really isn't an acceptable option in my opinion. I believe that regardless of the engineering complexities, the end users shouldn't have to feel pain in order to make engineering the solutions and features they interact with easier. Software is for end users (in their various forms) and as such we need to take that into account when we make decisions. While no functionality is lost per se, there is a major end-user impact, and that should be reason enough to implement it. John Postlethwait Nebula, Inc. 206-999-4492 On Tuesday, July 17, 2012 at 4:15 PM, Rouault, Jason (Cloud Services) wrote: One benefit is the user does not need to have multiple sets of credentials to interact with multiple projects. Jason From: openstack-bounces+jason.rouault=hp@lists.launchpad.net [mailto:openstack-bounces+jason.rouault=hp@lists.launchpad.net] On Behalf Of Adam Young Sent: Tuesday, July 17, 2012 11:55 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? On 05/29/2012 01:18 PM, Caitlin Bestler wrote: One of the major complication I see in the API is that users can be associated with multiple tenants. What is the benefit of this? What functionality would be lost if a human user merely had to use a different account with each tenant? There are numerous issues with multi-tenant users. For example, if a user is associated with multiple tenants, who resets the user's password? ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net
Re: [Openstack] Identity API v3 - Why allow multi-tenant users?
Joe, We find the domain approach very interesting for the private cloud scenario also. CERN has several large collaborations, each with multiple projects and independent quotas and roles. Using a 'default' domain, where OS_DOMAINNAME is not specified would be fine for our general use case. My question is if the user id name space is per domain or per IaaS instance ? I suspect this has significant implications in areas such as Horizon login and API compatibility. Tim From: Joseph Heck [mailto:he...@me.com] Sent: 18 July 2012 20:17 To: Tim Bell Cc: Adam Young; openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? Perhaps a poor analogy with email - The domain is an arbitrary string that's intended for tenant isolation in large openstack environments. It's a place to hang policy so that you can delegate things like password changing (where the keystone backend supports it) to someone other than the keystone-uber-administrator. I expect almost any smaller/smallish deployment of OpenStack to likely use just a single domain, which is mostly ignored. It's really a mechanism in place for service-provider sized clouds, or where you want to be able to enforce hard boundaries in permissions between groups of tenants by customizing the policy.json files to respect domain_id information. I would expect that in any implementation, it would be independent of email domain names or such - At least that wouldn't be a way that I'd slice up permissions across projects. -joe On Jul 18, 2012, at 9:25 AM, Tim Bell wrote: Thanks.. My worry is the username. Currently, I have OS_USERNAME=timbell Not OS_USERNAME=timb...@cern.ch Does that mean in the future that my OS_USERNAME=timbell OS_DOMAINNAME=cern.ch I would like that I could still register as timbell in my domain even if someone else on the same OpenStack instance has a user id of timbell. Cross domain, federated identity as part of an authorization layer would be an interesting development (as we look to federated clouds and bursting) but I didn't see something like that in v3. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Adam Young Sent: 18 July 2012 17:46 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? The idea of a Domain is that it is a single administrative entity, such as a company. When a person joins a company, they get an email adddress. THat address does not change regardless of the position they hold. Tenants are administrative groupings below that. It is unfortunate that we used the name tenants for this, as it actually contradicts the usual meaning of the term. We will be shortly switching back to using the term projects, and I think that is clearer. It certainly makes sense for a user to belong to one domain, but have access to a project controlled in another domain. Here is a scenario. Joe's Sporting Goods and Local Bank are both companies that have a presense in a coud provider. Each has their own domain. t...@localbank.com is going to set up a Point of Sale system for Joe. So Joe creates a project called joes-point-of-sale and provides access to user t...@localbank.com. On 07/18/2012 02:46 AM, Matt Joyce wrote: I could see service users and security / operations teams having a need to span many domains. -Matt On Tue, Jul 17, 2012 at 11:24 PM, Tim Bell tim.b...@cern.ch wrote: I thought that the v3 API supports domains as a group of tenants which would make the question rather different. Thus, I guess the question is A. Should there be users in multiple tenants in a single domain ? B. Should there be users in multiple domains ? There are clear use cases for A (such as researchers working on multiple projects sharing project quotas) For B, it is less clear as if I am a domain administrator, I do not want to be told that I cannot allocate user X since another domain has already taken it. On the other hand, there is a clear architectural benefit from having the concept of identity (and authentication) split off from roles and projects. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net] On Behalf Of John Postlethwait Sent: 18 July 2012 07:42 To: Rouault, Jason (Cloud Services) Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? Forcing a user to remember different usernames and/or passwords for each project they are a part of, when it is possible they are part of N projects, really isn't an acceptable option in my opinion. I believe that regardless of the engineering complexities, the end users shouldn't have to feel pain in order to make
Re: [Openstack] [Keystone] Quotas: LDAP Help
+1 The corporate LDAP should be read-only for a source of user, roles and attributes. Updating the corporate LDAP is not an option in many environments which can significantly benefit from the structured directory information available. Thus, at minimum, allow a r/o LDAP and local DB store for any openstack specific information that needs updating. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Ryan Lane Sent: 17 July 2012 20:43 To: Adam Young Cc: Joseph Heck; openstack Subject: Re: [Openstack] [Keystone] Quotas: LDAP Help I haven't been thinking about quotas, so bear with me here. A few thoughts: Certain deployments might not be able to touch the LDAP backend. I am thinking specifically where there is a corporate AD/LDAP server. I tried to keep the scheme dependency simple enough that it could be layered onto a read-only scenario. If we put quotas into LDAP, it might break on those deployments. Many, many deployments won't be able to. Applications should generally assume they are read-only in regards to LDAP. I can see that we don't want to define them in the Nova database, as Swift might not have access to that, and swift is going to be one of the primary consumers of Quotas. I am Assuming Quantum will have them as well. As you are aware, there is no metadata storage in the LDAP driver, instead it is generated from the tenant and role information on the fly. There is no place to store metadata in groupOfNames which is the lowest( common denominator) grouping used for Tenants. Probably the most correct thing to do would be to use a seeAlso that points to where the quota data is stored. Let's try not to force things into attributes if possible. When LDAP is used, is the SQL backend not used at all? Why not store quota info in Keystone's SQL backend, but pull user info from LDAP, when enabled? We should only consider storing something in LDAP if it's going to be reused by other applications. LDAP has a strict schema for exactly this purpose. If the quota information isn't directly usable by other applications we shouldn't store it in LDAP. Many applications with an LDAP backend also have an SQL backend, and use the SQL as primary storage for most things, and as a cache for LDAP, if it's used. I think this is likely a sane approach here, as well. - Ryan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom
Vish, How would the Nova migration from Essex to Folsom take place ? I'm wondering how we can validate Folsom without risking an existing Essex installation via some sort of clone/migrate operation. What is your assessment of the risk that Cinder is less stable than Nova volume ? Option 1 would give no option if there are issues, we would have either to stay on Essex entirely or wait until Folsom has the issues resolved. However, option 1 would be much cleaner code wise. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Vishvananda Ishaya Sent: 11 July 2012 17:27 To: Openstack (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom Hello Everyone, Now that the PPB has decided to promote Cinder to core for the Folsom release, we need to decide what happens to the existing Nova Volume code. As far as I can see it there are two basic strategies. I'm going to give an overview of each here: Option 1 -- Remove Nova Volume == Process --- * Remove all nova-volume code from the nova project * Leave the existing nova-volume database upgrades and tables in place for Folsom to allow for migration * Provide a simple script in cinder to copy data from the nova database to the cinder database (The schema for the tables in cinder are equivalent to the current nova tables) * Work with package maintainers to provide a package based upgrade from nova-volume packages to cinder packages * Remove the db tables immediately after Folsom Disadvantages - * Forces deployments to go through the process of migrating to cinder if they want to use volumes in the Folsom release Option 2 -- Deprecate Nova Volume = Process --- * Mark the nova-volume code deprecated but leave it in the project for the folsom release * Provide a migration path at folsom * Backport bugfixes to nova-volume throughout the G-cycle * Provide a second migration path at G * Package maintainers can decide when to migrate to cinder Disadvantages - * Extra maintenance effort * More confusion about storage in openstack * More complicated upgrade paths need to be supported Personally I think Option 1 is a much more manageable strategy because the volume code doesn't get a whole lot of attention. I want to keep things simple and clean with one deployment strategy. My opinion is that if we choose option 2 we will be sacrificing significant feature development in G in order to continue to maintain nova-volume for another release. But we really need to know if this is going to cause major pain to existing deployments out there. If it causes a bad experience for deployers we need to take our medicine and go with option 2. Keep in mind that it shouldn't make any difference to end users whether cinder or nova-volume is being used. The current nova-client can use either one. Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] [HPC] Openstack HPC telecon
Would it be possible a bit earlier ? This would be 10pm in Europe so it would limit the participation. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Narayan Desai Sent: 06 July 2012 17:08 To: John Paul Walters Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [HPC] Openstack HPC telecon On Fri, Jul 6, 2012 at 9:51 AM, John Paul Walters jwalt...@isi.edu wrote: Does something like the first Monday of the month at 4:00pm EDT (UTC-4) work? I'm just throwing out that time as something that seems to broadly work on my end, but I'd welcome any input from others. That generally works fine for me. -nld ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Openstack and Google Compute Engine
HPC is often used as a general term but it is actually many different facets depending on the computing model. CERN is at the centre of a server grid of 100,000s of servers called WLCG (http://wlcg.web.cern.ch) for analyzing the data from the Large Hadron Collider. The servers are located at over 200 sites worldwide in a tiered structure. However, we're more of High Throughput Computing (HTC) rather than HPC. HTC has a large number of programs running at the same time which have no need to talk to each other. Thus, it is more like a large scale batch farm than a massively parallel machine. While we lose a little performance on memory and I/O performance, virtualization brings major benefits in ease of management of the thousands of servers. We expect to be saving the few percent of overhead over the lifetime of machines by more flexibility scheduling repairs and placing the workload, such as overcommitting a hypervisor when one of the VMs is waiting for a tape to be mounted. Analysing the 25PB/year for the next 20 years, we're pretty intensive compute and I/O load. However, when we take the total cost of ownership, people included, we expect a significant efficiency gain from the use of a private cloud. Some more details at http://cern.ch/go/NH9w The massively parallel processing use cases with Crays/BlueGenes may not benefit from private clouds but many of the research sites will. Tim On 3 Jul 2012, at 16:12, Matt Joyce wrote: On Tue, Jul 3, 2012 at 2:01 AM, Simon G. semy...@gmail.commailto:semy...@gmail.com wrote: Secondly, I don't think we shouldn't compare GCE to Openstack. I understand that right now cloud (Openstack, Amazon, ...) is just easy in use, managed and scalable datacenter. It allows users to create VMs, upload their images, easily increase their (limited) demands, but don't you think that HPC is the right direction? I've always thought that final cloud's goal is to provide easy in use HPC infrastructure. Where users could do what they can do right now in the clouds (Amazon, Openstack), but also could do what they couldn't do in typical datacenter. They should run instance, run compute-heavy software and if they need more resources, they just add them. if cloud is unable to provide necessary resources, they should move their app to bigger cloud and do what they need. Openstack should be prepared for such large deployment. It should also be prepared for HPC use cases. Or if it's not prepared yet, it should be Openstack's goal. HPC in the cloud operates more like a grid computing solution. With things like Amazon HPC or HPC under openstack the idea is to allocate entire physical systems to a user on the fly. Traditionally to date that has been done with m1.full style instances. In many ways bare metal provisioning is a better option here than a hypervisor. And for many people who do work in an HPC environment bare metal really is the only solution that makes sense. The reality is that HPC use cases lose a lot of the underlying benefits of cloud infrastructure. So they really are something of an edge case at the moment. I believe that bare metal provisioning from within openstack could be a bit of a game changer in HPC, and that it could be useful in a wide variety of areas. But, ultimately I believe the usage that HPC in no way reflects general computing needs. And that really sums it up. Most folks do not need or want HPC. Most folks with HPC needs don't want a hypervisor slowing down their memory access. I know that clouds are fulfilling current needs for scalable datacenter, but it should also fulfill future needs. Apps are faster and faster. More often they do image processing, voice recognition, data mining and it should be clouds' goal to provide an easy way to create such advanced apps, not just simple web server which could be scaled up, by adding few VMs and load balancer to redirect requests. Infrastructure should be prepared even for such large deployment like that in google. It should also be optimized and support heavy computations. In the future it should be as efficient as grids (or almost as efficient), because ease of use has already been achieved. If, right now, it's easy to deploy VM into the cloud, the next step should be to optimize infrastructure to increase performance. Apps are actually slower and slower. The hardware is faster. The Applications themselves abstract more and more and thus slow down. As for what you do on your instances, that's entirely your own thing herr user. Some large data and some serious compute use cases simply don't lend themselves to cloud today. Hypervisors are limiting in so far as they give up some speed to provide the ability to share resources better. If you have no desire to share resources then virt machines become something of an impediment to you. So I don't see this as being accurate for some use cases. There are also other external limiting
Re: [Openstack] CY12-Q2 Community Analysis — OpenStack vs OpenNebula vs Eucalyptus vs CloudStack
The following may also be worth scanning: - http://forums.openstack.org/ - Mailing lists on http://wiki.openstack.org/MailingLists (although quite a few of them are quiet so would not affect the numbers much) Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Atul Jha Sent: 02 July 2012 08:50 To: Qingye Jiang (John); openstack@lists.launchpad.net Subject: Re: [Openstack] CY12-Q2 Community Analysis - OpenStack vs OpenNebula vs Eucalyptus vs CloudStack Hi, You should also add https://answers.launchpad.net/openstack Cheers!! Atul Jha From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Qingye Jiang (John) [qji...@gmail.com] Sent: Monday, July 02, 2012 7:50 AM To: openstack@lists.launchpad.net Subject: [Openstack] CY12-Q2 Community Analysis - OpenStack vs OpenNebula vs Eucalyptus vs CloudStack Hi all, I would like to let you know that I have just finished an analysis on the 4 open source projects (OpenStack, OpenNebula, Eucalyptus, CloudStack) from a community activity perspective. The analysis report could be found from my personal blog at http://www.qyjohn.net/?p=2233 (with a lot of figures). Best regards, Qingye Jiang (John) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Adding panel to a dashboard - Horizon
BTW, isn't the lack of option for a dashboard user to change their own
password considered as a missing functionality ?
Personally, if it was there, I'd like to turn it off (since we aim to use
Active Directory/LDAP) but for the standalone case, this would seem a
reasonable request.
Tim
From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
[mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Guillermo Alvarado
Sent: 04 June 2012 19:48
To: openstack@lists.launchpad.net
Subject: [Openstack] Adding panel to a dashboard - Horizon
Hi everyone!
I want to add a panel to settings dashboard. This panel is named 'Password'
and here the users will be able to modify your password (This will be
programmed).
My problem is that I can not add another panel (I dont see the option
Password in the Settings dashboard). I did the following:
1.- Added a folder named password in /horizon/dashboards/settings
2.- A added the __init__.py file into password folder
3.- Added the views.py file into password folder with this content:
from django import shortcuts
def index(request):
return shortcuts.render(request, 'settings/password/password.html',
{})
4.- Added urls.py file into password folder with this content:
from django.conf.urls.defaults import patterns, url
from .views import IndexView
urlpatterns = patterns('horizon.dashboards.settings.password.views',
url(r'^$', IndexView.as_view(), name='index'),
)
5.-Added panel.py file into password folder with this content:
from django.utils.translation import ugettext_lazy as _
import horizon
from horizon.dashboards.settings import dashboard
class Password(horizon.Panel):
name = _(Password)
slug = 'password'
dashboard.Settings.register(Password)
6.- In dashboard.py file located in /horizon/dashboard/settings added
password to panels:
panels = ('user', 'project', 'ec2', 'password')
But I not see the password panel. What is the problem?
Any answer will be apreciated, thanks in advance!
Best Regards,
Guillermo Alvarado
smime.p7s
Description: S/MIME cryptographic signature
___
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] Adding panel to a dashboard - Horizon
How about changing the default to be on ?
Demonstrating all the capabilities of a product while clearly documenting
(in an admin guide rather than source code) how to disable them seems to me
to be the way to showcase the software.
Tim
From: Tres Henry [mailto:t...@treshenry.net]
Sent: 04 June 2012 21:50
To: Tim Bell
Cc: Guillermo Alvarado; openstack@lists.launchpad.net
Subject: Re: [Openstack] Adding panel to a dashboard - Horizon
Keystone doesn't currently support querying for capabilities (i.e. what is
the Keystone auth backend) so Horizon defines a dict in local_settings that
can be used to specify the capabilities of Keystone in your deployment:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/l
ocal_settings.py.example#L61
By changing can_edit_user value you will either turn on, or off, the
capability to edit user accounts which includes changing password:
https://github.com/openstack/horizon/blob/master/horizon/dashboards/syspanel
/users/forms.py#L111
On Jun 4, 2012, at 12:22 PM, Tim Bell wrote:
BTW, isn't the lack of option for a dashboard user to change their own
password considered as a missing functionality ?
Personally, if it was there, I'd like to turn it off (since we aim to use
Active Directory/LDAP) but for the standalone case, this would seem a
reasonable request.
Tim
From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
[mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Guillermo Alvarado
Sent: 04 June 2012 19:48
To: openstack@lists.launchpad.net
Subject: [Openstack] Adding panel to a dashboard - Horizon
Hi everyone!
I want to add a panel to settings dashboard. This panel is named 'Password'
and here the users will be able to modify your password (This will be
programmed).
My problem is that I can not add another panel (I dont see the option
Password in the Settings dashboard). I did the following:
1.- Added a folder named password in /horizon/dashboards/settings
2.- A added the __init__.py file into password folder
3.- Added the views.py file into password folder with this content:
from django import shortcuts
def index(request):
return shortcuts.render(request, 'settings/password/password.html',
{})
4.- Added urls.py file into password folder with this content:
from django.conf.urls.defaults import patterns, url
from .views import IndexView
urlpatterns = patterns('horizon.dashboards.settings.password.views',
url(r'^$', IndexView.as_view(), name='index'),
)
5.-Added panel.py file into password folder with this content:
from django.utils.translation import ugettext_lazy as _
import horizon
from horizon.dashboards.settings import dashboard
class Password(horizon.Panel):
name = _(Password)
slug = 'password'
dashboard.Settings.register(Password)
6.- In dashboard.py file located in /horizon/dashboard/settings added
password to panels:
panels = ('user', 'project', 'ec2', 'password')
But I not see the password panel. What is the problem?
Any answer will be apreciated, thanks in advance!
Best Regards,
Guillermo Alvarado
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
smime.p7s
Description: S/MIME cryptographic signature
___
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] Adding panel to a dashboard - Horizon
Sounds like the folsom solution is the right way to go.. If the backend can
do it, offer it..
Tim
From: Tres Henry [mailto:t...@treshenry.net]
Sent: 04 June 2012 22:27
To: Tim Bell
Cc: Guillermo Alvarado; openstack@lists.launchpad.net
Subject: Re: [Openstack] Adding panel to a dashboard - Horizon
If you copy the local_settings.py.example it is on by default.
The Keystone team is adding functionality in Folsom to query for backend
capabilities so this will be more explicit in that timeframe. Until then,
simply copy local_settings.py.example.
On Jun 4, 2012, at 1:05 PM, Tim Bell wrote:
How about changing the default to be on ?
Demonstrating all the capabilities of a product while clearly documenting
(in an admin guide rather than source code) how to disable them seems to me
to be the way to showcase the software.
Tim
From: Tres Henry [mailto:t...@treshenry.net]
Sent: 04 June 2012 21:50
To: Tim Bell
Cc: Guillermo Alvarado; openstack@lists.launchpad.net
Subject: Re: [Openstack] Adding panel to a dashboard - Horizon
Keystone doesn't currently support querying for capabilities (i.e. what is
the Keystone auth backend) so Horizon defines a dict in local_settings that
can be used to specify the capabilities of Keystone in your deployment:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/l
ocal_settings.py.example#L61
By changing can_edit_user value you will either turn on, or off, the
capability to edit user accounts which includes changing password:
https://github.com/openstack/horizon/blob/master/horizon/dashboards/syspanel
/users/forms.py#L111
On Jun 4, 2012, at 12:22 PM, Tim Bell wrote:
BTW, isn't the lack of option for a dashboard user to change their own
password considered as a missing functionality ?
Personally, if it was there, I'd like to turn it off (since we aim to use
Active Directory/LDAP) but for the standalone case, this would seem a
reasonable request.
Tim
From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
[mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Guillermo Alvarado
Sent: 04 June 2012 19:48
To: openstack@lists.launchpad.net
Subject: [Openstack] Adding panel to a dashboard - Horizon
Hi everyone!
I want to add a panel to settings dashboard. This panel is named 'Password'
and here the users will be able to modify your password (This will be
programmed).
My problem is that I can not add another panel (I dont see the option
Password in the Settings dashboard). I did the following:
1.- Added a folder named password in /horizon/dashboards/settings
2.- A added the __init__.py file into password folder
3.- Added the views.py file into password folder with this content:
from django import shortcuts
def index(request):
return shortcuts.render(request, 'settings/password/password.html',
{})
4.- Added urls.py file into password folder with this content:
from django.conf.urls.defaults import patterns, url
from .views import IndexView
urlpatterns = patterns('horizon.dashboards.settings.password.views',
url(r'^$', IndexView.as_view(), name='index'),
)
5.-Added panel.py file into password folder with this content:
from django.utils.translation import ugettext_lazy as _
import horizon
from horizon.dashboards.settings import dashboard
class Password(horizon.Panel):
name = _(Password)
slug = 'password'
dashboard.Settings.register(Password)
6.- In dashboard.py file located in /horizon/dashboard/settings added
password to panels:
panels = ('user', 'project', 'ec2', 'password')
But I not see the password panel. What is the problem?
Any answer will be apreciated, thanks in advance!
Best Regards,
Guillermo Alvarado
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
smime.p7s
Description: S/MIME cryptographic signature
___
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] Openstack with CentOS 6.2
If youre using puppet for configuration management, we would strongly recommend the puppetlabs openstack modules. They handle all the distribution differences too... They're working great for us with Scientific Linux so CentOS should work well too... Tim CERN -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Pádraig Brady Sent: 31 May 2012 16:44 To: Vogel Nicolas Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Openstack with CentOS 6.2 On 05/31/2012 03:22 PM, Pádraig Brady wrote: On 05/31/2012 08:39 AM, Vogel Nicolas wrote: Hi everybody, Im trying to install Openstack (Essex release) with CentOS 6.2 and I have a lot of problems because of dependencies and a deficiency of installation documents. I think I get all the actual packages and I try to make the install with the official doc, which is based on Ubuntu. So I have to search and modify at every step, and thats very difficult for me. For example, beginning with keystone, the syntax for creating tenant, users and roles is different. The keystone.conf file must be changed too. And then I tried to continue with glance, but both .ini files are missing and I dont know if I have to create them or if I have to adapt the .conf files. If someone could give me documentation or a link for the installation of Essex release on CentOS/RHEL 6.2, I would be really gratefull. The best approach at this stage is to use the packages from EPEL. https://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL The openstack upstream docs are currently in the process of being updated with much of this info. Actually Anne's suggestion of following the official docs (that she's sending you a preview of) is much better. They're much more integrated and in-depth. You can use the URL above as a cross reference for issues etc. cheers, Pádraig. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] [OpenStack][Nova] deference between live-migration and migrate
I would favour a field for the type of migration which allows future expansion. we've already got migrate, live migrate and block migrate but hypervisors may have further different flavours too in the future and the API should support the full set of options while encouraging convergence when there are common functionalities. How about we move the API flag to a text field for the migration type ? For private clouds without billing concerns, a snapshot/restart option may be more attractive. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of David Kranz Sent: 31 May 2012 20:29 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate On 5/31/2012 2:10 PM, Vishvananda Ishaya wrote: On May 25, 2012, at 2:36 AM, John Garbutt wrote: I have been meaning to draft a blueprint around this. What we have today: . Migrate: move a VM from one server to another, reboots across the move (I think) and destination is picked by scheduler . LiveMigration: move a VM form one server to another, VM doesn't appear to reboot, need to specify the destination I propose we extent the Migrate API (thinking about nova CLI here really) to include: . Optional Flag to force non-live migration, default to live migration . Optional destination host, by default let the scheduler choose . Deprecate the existing live migration API and CLI calls What do people think? +1 Keep in mind that we actually have three options: live migration on shared storage live migration without shared storage (block migration) resize/migrate Yun actually suggested that resize/migrate be simplified to do the following instead of scping the file over: * snapshot to glance * boot new image from snapshot This would definitely simplify the code, unfortunately it could have billing/metering repercussions. Vish I don't think it is documented that you need to set up ssh with credentials between compute nodes to make resize and block migration work. I also heard something about there being a more secure way to do this than setting up ssh in this way. What is the officially recommended way to configure compute nodes for these operations? -David smime.p7s Description: S/MIME cryptographic signature ___ 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] Identity API v3 - Why allow multi-tenant users?
In the research environment, we have frequent cases where a user is associated with multiple tenants. For example, when you are finishing work on a previous project but are mainly working on the new one. As we move towards domain/tenant/user, we need to ensure that the tools support multi-tenant per user. Correct accounting is critical. This does require extra code but it is relevant given the use cases. Tim Bell CERN From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Caitlin Bestler Sent: 29 May 2012 19:18 To: openstack@lists.launchpad.net Subject: [Openstack] Identity API v3 - Why allow multi-tenant users? One of the major complication I see in the API is that users can be associated with multiple tenants. What is the benefit of this? What functionality would be lost if a human user merely had to use a different account with each tenant? There are numerous issues with multi-tenant users. For example, if a user is associated with multiple tenants, who resets the user's password? smime.p7s Description: S/MIME cryptographic signature ___ 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] Deployments in Scientific Environments
CERN is more of a high throughput computing environment rather than a high performance site. Although we do multi-core, our programs are not the large scale floating point programs of some other sciences, so GPUs etc. are not a significant gain for us. CERN is currently targeting a pre-production service based on OpenStack this year and targetting around 15,000 hypervisors spread across two data centres by 2015. For a quick overview, see http://cern.ch/go/NH9w Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Thierry Carrez Sent: 24 May 2012 11:46 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Greatest deployment? SoLa wrote: Few days ago I read something about OpenNebula,it's the main competitor in open source for Openstack, beside Eucalyptus, as far as i know. OpenNebula and Eucalyptus (as well as CloudStack) are alternative solutions in the open source IaaS Compute space. Note that OpenStack provides more than just IaaS Compute feature (Nova), it also addresses object storage (Swift), or network (Quantum)... I found (http://blog.opennebula.org) something about tens of thousands of VMs and OpenNebula's performance (maybe CERN has such huge deployment, who knows they didn't mention that) and I'm just wondering what about Openstack performance. Can anyone praise about biggest deployments? How many VMs can Openstack actually supervise? Any large- scale achievements? OpenStack is being used to power public clouds (HP, Rackspace, ATT, Internap, Korea Telecom, SDSC...). Those are unfortunately notoriously shy at sharing size numbers :) OpenNebula has also this advantage, for me, that it's designed also to provide scientific cloud and it's used by few research centres and even supercomputing centres. How about Openstack? Anyone tried deploy it in supercomputing environment? Maybe huge cluster or GPU cluster or any other scientific group is using Openstack? Is anyone using Openstack in scentific environement or Openstack's purpose is to create commercial only cloud (business - large and small companies)? OpenStack is being used in a number of research clouds, including NeCTAR (Australia's national research cloud). There is huge interest around bridging the gap there, with companies like Nimbis or Bull being involved. Hopefully people with more information than I have will comment on this thread. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] [Keystone] PKI
Fully agreed. Academic and Research sites have extensive X.509 infrastructure that we would not wish to duplicate. Are you only looking at user certificates or are host certificates in the scope too ? Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Adam Young Sent: 16 May 2012 03:10 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [Keystone] PKI Well, the PKI pieces are the same regardless of the CA and certificate issuing pieces. All we will need to do is to use a signing key to sign a document. So EJBCA or Dogtag will work equally as well. If people already have a CA infrastructure, they should be able to leverage that, too. On 05/15/2012 04:47 PM, Thor Wolpert wrote: If you're open to levarging other OSS projects, http://www.ejbca.org/architecture.html us a great one to look at, assuming you need a PKI implementation available. I believe it is at least worth a look. On Tue, May 15, 2012 at 1:30 PM, Razique Mahroua razique.mahr...@gmail.com wrote: great topic :) mailto:he...@mac.com Joseph Heck 15 mai 2012 21:06 Coming out of the Keystone meeting from today (http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-me eting.2012-05-15-18.02.html), I thought it worth mentioning that adam young has been doing some tremendous lifting in terms of looking at adding in PKI support to Keystone. The writeup and details are on the OpenStack wiki at http://wiki.openstack.org/PKI I rather suspect there's a lot of interest in this topic, so I wanted to make sure the broader community knew about the effort, what we were thinking, and were we are. If you're interested in discussing, the keystone meeting is on Tuesday mornings at 18:00 UTC -joe ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- Nuage Co - Razique Mahroua razique.mahr...@gmail.com ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] i18n of log message
I would also vote for an application prefix and error number for easy searching. It is also great when you have to write the problem determination guides. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of ?? Sent: 01 May 2012 10:47 To: Andrew Hutchings Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] i18n of log message 2012/5/1 Andrew Hutchings and...@linuxjedi.co.uk Hi 彭勇, On 01/05/12 03:38, 彭勇 wrote: the log messages of OpenStack are i18n now. i propose to use english only log messages: 1. if any one have problem, they can shared with others more easy. he can search english message, and send message to maillist. if the log message is i18n, a Chinese version message can't shared to Japanese. 2. if we have i18n log message, it's hard to update log message. we should update every localization version of message. This was all actually covered in the i18n talk at the developer's summit: http://etherpad.openstack.org/FolsomI18N The information in there says mailing list says no, feedback from session says yes (especially requested by operators in china) - need a vote? compare to apache projects... we are guys in China. we have a openstack group more than 500 members. we can promote a vote for this I do also remember a suggestion of translated error messages and a common error code (such as NOV1234 I guess?) to use in places such as a Google search (such as MySQL does). You could then search for the translated error message or the code if you feel your language skills are good enough to get multi-lingual results. Oracle handle error message this way, for example: ORA-01000: maximum open cursors exceeded it's hard to maintain multi-lingual log message for open source project. Since we are going to be reworking i18n very soon I suspect feedback would be welcome. Kind Regards -- Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 彭勇 (Peng Yong) ___ 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
Re: [Openstack] Open Cloud Computing Interface Blueprint Implementation
Andy, Thanks for this work. OCCI is an interesting and open option as the world moves towards federated clouds. I hope that this will continue the momentum towards an open API which can address multiple backend IaaS solutions transparently. Tim Bell CERN From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Michel Drescher Sent: 16 April 2012 18:00 To: Edmonds, AndrewX Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Open Cloud Computing Interface Blueprint Implementation Dear Andy, all, There is little left to say for me (thanks to others) but a wholeheartedly Bravo! on the effort. As Matteo and others have stated, it is important to have a publicly defined standard being implemented in production grade software. But much more important, certainly from an EGI perspective, is the availability of *choice* of implementation for anyone who wishes to operate a Cloud platform. For us at EGI it is of particular importance as we are working towards a production level federation of IaaS Cloud offerings, as a federation cannot prescribe which particular software implementation to operate. With the availability of OCCI in OpenStack, we now are in the place to actually see our endorsement for OCCI to happen in in reality rather on paper. What's more, native support for OCCI particularly makes the choice for OpenStack attractive, as this means not only less operative service management effort for a fronting proxy service (I hope!), but also, lets say, less opportunity for configuration and operation mistakes. :-) Cheers, and thanks again, Michel -- Stichting European Grid Initiative (EGI.eu) http://www.egi.eu Mobile:+31 (0)6 303 726 55 Skype: michel.drescher.egi ___ 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] [Ops] OpenStack and Operations: Input from the Wild
Availability metrics for me are ones that allow me to tell if the service is up, degraded or down. Each of us as we start production monitoring need to work out how many nova, glance and swift processes of which type should be running. Furthermore, we need to add basic 'ping' style probes to see that the services are responding as expected. Performance metrics are for cases where we want to record how well the system is running. Examples of number of REST calls/second, VMs created/second etc. These are the kind of metrics which feed into capacity planning, bottleneck identification, trending. Building up an open, standard and consistent set will avoid duplicate effort as sites deploy to production and allow us to keep the monitoring up to date when the internals of OpenStack change. Tim From: Huang Zhiteng [mailto:winsto...@gmail.com] Sent: 09 April 2012 05:42 To: Tim Bell Cc: David Kranz; Andrew Clay Shafer; openstack-operat...@lists.openstack.org; Duncan McGreggor; openstack Subject: Re: [Openstack] [Ops] OpenStack and Operations: Input from the Wild Hi Tim, Could you elaborate more on 'performance metrics'? Like what kind of metrics are considered as performance ones? Thanks. On Sat, Apr 7, 2012 at 2:13 AM, Tim Bell tim.b...@cern.ch wrote: Splitting monitoring into 1. Gathering of metrics (availability, performance) and reporting in a standard fashion should be part of OpenStack. 2. Best practice sensors should sample the metrics and provide alarms for issues which could cause service impacts. Posting of these alarms to a monitoring system should be based on plug ins 3. Reference implementations for standard monitoring systems such as Nagios should be available that queries the data above and feeds it into the package selected Each site does not want to be involved in defining the best practice. Equally, each monitoring system should not have to have an intimate understanding of OpenStack to produce a red/green light. The components for 1 and 2 fall under the associated openstack component. Component 3 is the monitoring solution provider. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net] On Behalf Of David Kranz Sent: 06 April 2012 16:44 To: Andrew Clay Shafer Cc: openstack-operat...@lists.openstack.org; openstack; Duncan McGreggor Subject: Re: [Openstack] [Ops] OpenStack and Operations: Input from the Wild This is a really great list! With regard to cluster health and monitoring, I did a bunch of stuff with Swift before turning to nova and really appreciated the way each swift service has a healthcheck call that can be used by a monitoring system. While I don't think providing a production-ready monitoring system should be part of core OpenStack, it is the core architects who really know what needs to be checked to ensure that a system is healthy. There are various sets of poking at ports, process lists and so on that Crowbar, Zenoss, etc. set up but it would be a big improvement for deployers if each openstack service provided healthcheck apis based on expert knowledge of what is supposed to be happening inside. That would also insulate deployers from changes in the code that might impact what it means to be running properly. Looking forward to the discussion. -David On 4/6/2012 1:06 AM, Andrew Clay Shafer wrote: Interested in devops. Off the top of my head. live upgrades api queryable indications of cluster health api queryable cluster version and configuration info enabling monitoring as a first class concern in OpenStack (either as a cross cutting concern, or as it's own project) a framework for gathering and sharing performance benchmarks with architecture and configuration On Thu, Apr 5, 2012 at 1:52 PM, Duncan McGreggor dun...@dreamhost.com wrote: For anyone interested in DevOps, Ops, cloud hosting management, etc., there's a proposed session we could use your feedback on for topics of discussion: http://summit.openstack.org/sessions/view/57 Respond with your thoughts and ideas, and I'll be sure to add them to the list. Thanks! d ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack
Re: [Openstack] [Ops] OpenStack and Operations: Input from the Wild
Splitting monitoring into 1. Gathering of metrics (availability, performance) and reporting in a standard fashion should be part of OpenStack. 2. Best practice sensors should sample the metrics and provide alarms for issues which could cause service impacts. Posting of these alarms to a monitoring system should be based on plug ins 3. Reference implementations for standard monitoring systems such as Nagios should be available that queries the data above and feeds it into the package selected Each site does not want to be involved in defining the best practice. Equally, each monitoring system should not have to have an intimate understanding of OpenStack to produce a red/green light. The components for 1 and 2 fall under the associated openstack component. Component 3 is the monitoring solution provider. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of David Kranz Sent: 06 April 2012 16:44 To: Andrew Clay Shafer Cc: openstack-operat...@lists.openstack.org; openstack; Duncan McGreggor Subject: Re: [Openstack] [Ops] OpenStack and Operations: Input from the Wild This is a really great list! With regard to cluster health and monitoring, I did a bunch of stuff with Swift before turning to nova and really appreciated the way each swift service has a healthcheck call that can be used by a monitoring system. While I don't think providing a production-ready monitoring system should be part of core OpenStack, it is the core architects who really know what needs to be checked to ensure that a system is healthy. There are various sets of poking at ports, process lists and so on that Crowbar, Zenoss, etc. set up but it would be a big improvement for deployers if each openstack service provided healthcheck apis based on expert knowledge of what is supposed to be happening inside. That would also insulate deployers from changes in the code that might impact what it means to be running properly. Looking forward to the discussion. -David On 4/6/2012 1:06 AM, Andrew Clay Shafer wrote: Interested in devops. Off the top of my head. live upgrades api queryable indications of cluster health api queryable cluster version and configuration info enabling monitoring as a first class concern in OpenStack (either as a cross cutting concern, or as it's own project) a framework for gathering and sharing performance benchmarks with architecture and configuration On Thu, Apr 5, 2012 at 1:52 PM, Duncan McGreggor dun...@dreamhost.com wrote: For anyone interested in DevOps, Ops, cloud hosting management, etc., there's a proposed session we could use your feedback on for topics of discussion: http://summit.openstack.org/sessions/view/57 Respond with your thoughts and ideas, and I'll be sure to add them to the list. Thanks! d ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] OpenStack immaturity
Essex is a key release in this respect. With the excellent work done by the developers, testers and packaging teams, OpenStack is much better positioned than with Diablo. As the work proceeds on Folsom, back porting critical bugs and planning for a smooth migration path for production sites will become factors in keeping the early adopters enthusiastic. These are the user stories that will drive the next wave of OpenStack growth as much as expanding the feature set. Tim Bell CERN From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Jan Drake Sent: 04 April 2012 16:37 To: Razique Mahroua Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] OpenStack immaturity H. While ease of deployment is definitely an area of future strength for OS, the gap is closing rapidly and the reality for the enterprise is that initial, comparable (apples to apples) VMWare installations all come with an initial professional services engagement anyway. Having just done a bake-off twixt the latest OS builds and VMWare for creating an enterprise private IaaS cloud, my strategic money's on OpenStack and the community is starting to make significant in-roads on the tactical value as well. Lots of areas of future strength but the promise remains immense and the feasibility for the enterprise continues to grow. Keep up the good work. Keep Calm, Carry On, and all that. Jan PS: Anybody got an extra ticket to the design summit? On Apr 4, 2012, at 6:14 AM, Razique Mahroua razique.mahr...@gmail.com wrote: The immaturity being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment. Such statements are not new, and well known from enterprises point of view. I remember same articles about Linux, few years back about Zimbra, few months back about proxmox, etc... This is an endless statement : Is it possible for a community-driven project to find it's place in business needs ? The answer for Openstack is NO, when it comes to ease of deployment compared to VMmware, and any CLI-less required installers... But even if fantastic progress has been made, on the different projects, let's face it, even more progress are required today to give a satisfaction to the OP. Let's keep working as we are doing : fixing, testing, thinking, updating. When all the projects will be stable enough to work on a same level - I'm quite confident we could see more positives feedbacks from Gartner Nuage Co - Razique Mahroua razique.mahr...@gmail.com NUAGECO-LOGO-Fblan_petit.jpg Le 4 avr. 2012 à 14:48, Jacek Artymiak a écrit : It depends on what you expect OpenStack to do for you. If you want pre-packaged, click-to-install software, it is not there, yet. But if you want to be able to influence the future of the project you want to bet your business on, you have a much higher chance of doing that with OpenStack than with other projects in this space. Just my $.02 worth. Jacek Artymiak author: http://docs.openstack.org/api/openstack-compute/programmer/content/ (please submit patches so we can improve this document) On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] nova zone and availability_zone
It would be useful if there was a glossary of terms related to Openstack. It is easy to get confused as many words are overloaded or slightly different between different parts of Openstack. There is also the page on identity at http://docs.openstack.org/diablo/openstack-identity/admin/content/Identity- Service-Concepts-e1362.html http://docs.openstack.org/diablo/openstack-identity/admin/content/Identity-S ervice-Concepts-e1362.html which defines some concepts. From http://wiki.openstack.org/Glossary http://wiki.openstack.org/Glossary, there is a pointer to http://cloudglossary.com/ http://cloudglossary.com/ but the openstack terms are not in there. There is also http://docs.openstack.org/incubation/openstack-network/developer/quantum-ap i-1.0/content/Glossary.html http://docs.openstack.org/incubation/openstack-network/developer/quantum-api -1.0/content/Glossary.html for networking. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Sandy Walsh Sent: 20 March 2012 12:07 To: Nicolae Paladi; openstack@lists.launchpad.net Subject: Re: [Openstack] nova zone and availability_zone Availability Zone is an EC2 concept. Zones were a sharding scheme for Nova. Zones are being renamed to Cells to avoid further confusion. Availability Zones will remain the same. Hope it helps! -S _ From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Nicolae Paladi [n.pal...@gmail.com] Sent: Tuesday, March 20, 2012 6:55 AM To: openstack@lists.launchpad.net Subject: [Openstack] nova zone and availability_zone Hi all, What is the difference between nova zone(s) and availability_zone? In a new deployment, the *services* table in the nova db contains an availability_zone column (which is 'nova', but default). If that is not the same as nova zones (which are logical deployments, as far as I understood), where is information about zones stored? The only documentation about zones in openstack that I could find is here: http://nova.openstack.org/devref/zone.html is there anything on availability zones? Cheers, /Nicolae. smime.p7s Description: S/MIME cryptographic signature ___ 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] availability/performance sensors/probes
This does bring up a more generic problem of sharing the availability/performance code for all of the OpenStack components. At the design summit, this was proposed as one of the example use cases of the OpenStack community forge (I forget the exact name) but it was intended as a place for sharing code/procedures which were not intended to be part of the core but may be of interest to others. Was anything set up along these lines ? A set of production quality Nagios/Ganglia sensors would be very interesting if someone has these Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Jasper Capel Sent: 21 February 2012 18:29 To: John Dickinson Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] swprobe: swift middleware for sending metrics to graphite using statsd Hi John, Apparently my google-fu is not up to snuff, as I wasn't aware of that project. Had I been, I probably would've just extemded that one. :) Cheers, Jasper From: John Dickinson [m...@not.mn] Sent: Tuesday, February 21, 2012 5:44 PM To: Jasper Capel Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] swprobe: swift middleware for sending metrics to graphite using statsd That's great. Have you by any chance seen https://github.com/pandemicsyn/swift-informant? It's something similar that we've been playing with at Rackspace. --John On Feb 21, 2012, at 10:36 AM, Jasper Capel wrote: Hi all, I'm announcing a piece of Swift middleware, swprobe [1], designed to gather run-time metrics and ship them off to Graphite [2] for near real-time monitoring. Currently it sends out bytes up- and downloaded per account, http methods and response codes and timings in miliseconds on each call. To be able to use this you need Graphite [2]. You also need statsd running, preferably on the local machine since there potentially many small UDP packets are being sent out. Please also note that we have not yet tested this with production workloads. [1] - https://github.com/spilgames/swprobe [2] - http://graphite.wikidot.com/ [3] - https://github.com/etsy/statsd Best regards, -- Jasper Capel Lead Infrastructure Engineer W http://www.spilgames.com | S jwcapel-spil ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] Remove Zones code - FFE
Fully agree with the prefix for the cell... there should be storage-cells and compute-cells with different goals in terms of data locality and availability, zone has become too overloaded... Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Mark Washenberger Sent: 19 February 2012 19:54 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Remove Zones code - FFE Remember that for many deployments, the entire system will be a single zone, so whatever term is used should make sense in a singular sense. That rules out names such as 'slice' or 'fragment'. I think this is a slightly outdated concept of zones. The key to scalability in nova is to divide the set of all compute nodes into subsets, each with its own messaging and database infrastructure. The granularity of everything else (scheduling, api, volume, network, what-have- you) is just an implementation or deployment detail that should be flexible depending on our ultimate implementation and any alternative strategies we expose to deployers. With this in mind it's still true that the smallest deployment would be likely include just one compute zone (or compute cell, as we are trending). But that is a far cry from the whole system even in a small deployment. For this reason, whatever name we choose I would hope we prefix it with compute- (i.e. compute-zone or compute-cell) so that we aren't letting language trick us out of some of our better implementation options, such as allowing deployers to scale compute, volume, network, and api resources separately. Ed Leafe ed.le...@rackspace.com said: On Feb 18, 2012, at 1:08 PM, Nathanael Burton wrote: Sectors remind me too much of disks. Agreed. How about? Layers, Slices, Fragments, Knots... Remember that for many deployments, the entire system will be a single zone, so whatever term is used should make sense in a singular sense. That rules out names such as 'slice' or 'fragment'. 'Knot'? In what sense can 'knot' be used? I still prefer 'cell'. The parallel to single celled / multi-cellular life forms makes sense, and there is really no overloading of the word in the world of computers. -- Ed Leafe ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] [Nova] Essex dead wood cutting
With the Hyper-V support being phased out, I would be interested to understand: - What hypervisors are being used for running Windows guests (both Windows 7 and Windows Server) on top of OpenStack ? - To what extent will Microsoft support problems reported with a Windows guest running on a non-Microsoft hypervisor ? - Are there other sites who are affected by this proposal who would be willing to invest effort to maintain the Hyper-V support ? Tim Bell CERN -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Sandy Walsh Sent: 27 January 2012 16:45 To: Thierry Carrez; openstack@lists.launchpad.net Subject: Re: [Openstack] [Nova] Essex dead wood cutting I'll be taking the existing Zones code out of API and Distributed Scheduler. The new Zones infrastructure is an optional component. -S From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Thierry Carrez [thie...@openstack.org] Sent: Friday, January 27, 2012 11:23 AM To: openstack@lists.launchpad.net Subject: [Openstack] [Nova] Essex dead wood cutting Just as Nova enters feature freeze, it sounds like a good moment to consider removing deprecated, known-buggy-and-unmaintained or useless feature code from the Essex tree. Here are my suggestions for removal: - Ajaxterm (unmaintained, security issues, replaced by VNC console) - Hyper-V support (known broken and unmaintained) I'm sure that everyone has suggestions on other dead wood that we should cut now rather than ship in Essex... please comment. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ 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] nova/puppet blueprint, and some questions
Looks interesting. I wonder if it can be made more generic so that it would satisfy a similar set of requirements for Chef (or whatever else comes along). I would suspect that the general requirements for tables etc. are not puppet specific, although the implementations may vary. I would hope for, at minimum, an implementation for Xen and KVM with, if appropriate, something for lxc too. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Andrew Bogott Sent: 26 January 2012 19:26 To: openstack@lists.launchpad.net Subject: [Openstack] nova/puppet blueprint, and some questions Happy tag day, everyone! The next thing I'm going to work on (for Nova/Folsom) is adding an API to assist with Puppet configuration on nova instances. The blueprint for that is here: http://wiki.openstack.org/PuppetConfigForNova I welcome comments on that proposal. There's a fair bit of hand-waving in the Implementation section when it comes to the question of how exactly Nova will communicate puppet config to an instance. Ideally I would like to use file injection to drop a site.pp file directly onto the instance. My fear, though, is that file injection is not supported widely enough for me to rely on it. Is that right? Are there plans to support file injection on non-Xen hypervisors (most importantly, on KVM?) If I can't rely on file injection, then I probably need to use metadata instead. Is metadata injection more widely supported than file injection? And, is there any kind of 'standard' pattern for instance daemons that notice and respond to metadata changes (e.g. the guest agents module), or would I just adlib that part? Thanks! -Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ 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] Swift client tool
A Dropbox like 'sync' function would be very interesting.. does anyone know one which is compatible with OpenStack Swift ? Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Kuo Hugo Sent: 19 December 2011 17:38 To: Prakashan Korambath Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Swift client tool Several options 1. Cyberduck (for Mac Win only) , swift will present like a FTP server user experience for you 2. Gladinet desktop (free version) , under gladinet , you might get feel swift more like a NAS device ... but only for static object files , not that easy to setup a gladinet compatible swift environment . It requires SSL and validate SSL certification . Only for Win OS 3. Under Linux , you can leverage swift client , the easiest way is #apt-get install swift 4. Write your own client by call swift client module 5. Write your own client through swift API endpoint 6. Using OpenStack Dashboard , it includes Swift feature. but it requires keystone integration 7. develop your own Web server for access Swift We can confirm all approaches above . but might need to dig out some more tricky skill from google . If your swift only for personal usage , you can easily install cyberduck to access swift. In my using , I just need to setup auth server endpoint manually in cyberduck's configuration file to point the correct auth server endpoint which depends on your auth server . more information plz goole it . Feel free to drop your question over here . I'll have an answer for you as I can. +Hugo Kuo+ tonyt...@gmail.commailto:tonyt...@gmail.com hugo@cloudena.commailto:hugo@cloudena.com +886-935-004-793 www.cloudena.comhttp://www.cloudena.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] Providing packages for stable releases of OpenStack
Thierry, I'm not clear on who will be maintaining the stable/diablo branch. The people such as EPEL for RedHat systems need to have something with the appropriate bug fixes back ported. There are an increasing number of sites looking to deploy in production and cannot follow the latest development version. Tim ___ 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] Providing packages for stable releases of OpenStack
We need more than 'just' packaging it is using the testing, documentation and above all care to produce *and* maintain a stable release that production sites can rely on for 6-12 months and know that others are relying on it too. Who is going to make the judgement that a bug fix to the latest Essex development branch is a valid patch for a backport to stable/diablo and does not break production sites ? Diablo 2011.3 brought much functionality but also some useful points to consider for the future as to how we organise the project. Tim (4) OpenStack will accept and foster a new project, one that is not focused on development, but rather the distribution and it's general stability. This distro project will be responsible for advocating on behalf of various operating systems/distros/sponsoring vendors for bugs that affect performance and stability of OpenStack, or prevent an operating system from running OpenStack. Thoughts? d Hi We already have an little informal channel on freenode called #openstack-packaging. Regards chuck ___ 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
Re: [Openstack] Providing packages for stable releases of OpenStack
The stable team with Duncan's additions would fully address my concerns. Tim ___ 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] Openstack Packaging
We would be very interested to know where we can get a recent, stable Diablo++ release for RHEL 6. We appreciate the speed of development for Essex but there is also a need for a pre-tested base on Diablo+fixes stable functionality for the potential production users to integrate to. Tim Bell CERN ___ 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] openstack-satellite
Let's not raise the bar too high for Satellite The points mentioned (CI, QA, etc.) should be clearly documented with a y/n for the projects to aid selection but I would much rather try out a non-CI tool in the directory than have to write it all myself from scratch. Ultimately, the aim of Satellite is that it is quicker to find a solution and lower effort to run it than to write it yourself. Tim ___ 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] API Spec
I have an api, diablo nova v1.1. What we are talking about is if it covers 100% functionality. I can start my deployment testing with v1.1. The limiting factor is not v1.1 vs v1.x for most sites. It is packaging, user exits and integration, not whether feature X is in the latest API. Tim. - Reply message - From: George Reese george.re...@enstratus.com To: Tim Bell tim.b...@cern.ch Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: [Openstack] API Spec Date: Sat, Aug 27, 2011 20:47 A cloud platform simply isn't functional without an API. It is a core requirement. No API, no cloud. -George On Aug 27, 2011, at 7:04 PM, Tim Bell wrote: I'm also a non-API expert but getting a stable open cloud engine with a reasonable API would seem to be a good target before we look to enhance it. There are lots of potential users of Nova (including Rackspace) who would like to get Nova into production. An API will fully exploits all of the underlying functionality should be discussed/planned in the longer term but let's get Diablo out and deployable first. Tim Bell CERN ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com To schedule a meeting with me: http://tungle.me/GeorgeReese ___ 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] Thinking about Backups/Snapshots in Nova Volume
As regards the backup/snapshots From our use cases on service consolidation for production servers, we'd like to be able to - support frequent snap shots, ideally to also make those snapshots easily available in Glance for test machine clone operations - replicate those snapshots to other sites to allow for disaster recovery - allow long term archiving to S3 such as historical images for data preservation Being able to associate a VM image snapshot with a block storage snapshot so that the entire state of a machine and its external volumes can be recovered together would be very useful for these disaster recovery scenarios. Tim Bell CERN ___ 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] Thinking about Backups/Snapshots in Nova Volume
The terms for snapshot and backup seem completely reasonable. From a server consolidation/disaster recovery point of view, the dream would be to be able to do backup and snapshot mirroring, almost like an Oracle dataguard, to a remote site. From my understanding of the upcoming Swift container replication features, this would be feasible if we can get the data into Swift. Tim ___ 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] Cross-zone instance identifiers in EC2 API - Is it worth the effort?
At the risk of making things more complicated, we should anticipate an eventual Cloud API standard which could be any solution from EC2/OpenStack/OCCI/... and a set of legacy interfaces for backwards compatibility. This, as far as I see, pushes us strongly towards the multiple APIs as a presentation layer and a backend which is relatively flexible (as we also can adapt the presentation layers to convert if required without impacting the clients). Some interfaces, such as the OpenStack one could be relatively light and the additional business logic of mapping/transforming added to the other interfaces as required. Tim Bell CERN ___ 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] Queue Service, next steps
Please bear in mind the long term maintainability of the openstack package. One of the attractive features at the moment is that there are not significant pre-reqs to set up the environment and most mass market environments can support it. Using C++ would not significantly change this situation, whereas using Erlang may create some more difficulty further down the line. Anything that makes porting/rebuilding more difficult needs to be carefully thought through. Tim Bell CERN ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
