Re: [Openstack] Havana-2 development milestone available

[Michael Basnight]

On Jul 18, 2013, at 12:05 PM, Thierry Carrez wrote:

> Hi everyone,
> 
> The second milestone of the Havana development cycle, "havana-2" is now
> available for Keystone, Glance, Nova, Horizon, Neutron, Cinder,
> Ceilometer, and Heat. In the last 7 weeks, more than 100 features were
> added and more than 650 bugs fixed.
> 
> You can see the full list of new features and fixed bugs, as well as
> tarball downloads, at:
> 
> https://launchpad.net/keystone/havana/havana-2
> https://launchpad.net/glance/havana/havana-2
> https://launchpad.net/nova/havana/havana-2
> https://launchpad.net/horizon/havana/havana-2
> https://launchpad.net/neutron/havana/havana-2
> https://launchpad.net/cinder/havana/havana-2
> https://launchpad.net/ceilometer/havana/havana-2
> https://launchpad.net/heat/havana/havana-2
> 
> The next (and last) development milestone of the Havana cycle, havana-3,
> is scheduled for September 6th (final release is planned October 17th).

And let us not forget our incubated program, Trove, and its milestone!!

https://launchpad.net/trove/havana/havana-2



___
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] CLI username and password prompt

[Michael Basnight]

On Jul 16, 2013, at 11:48 PM, Jake G. wrote:

> Using RDO Packstack 

>From http://openstack.redhat.com/Quickstart

Once the process is complete, you can log in to the OpenStack web interface 
"Horizon" by going tohttp://$YOURIP/dashboard. The username is "admin". The 
password can be found in the file keystonerc_admin in the /root/ directory of 
the control node.


___
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] CLI username and password prompt

[Michael Basnight]

On Jul 16, 2013, at 11:39 PM, Jake G. wrote:

> OK got the URL to work but now I get the error "ERROR: Invalid OpenStack Nova 
> credentials"
> 
> What should the default credentials be or is there a place this is stored?

If you are using devstack you should be able to source ~/devstack/openrc, and 
it will provide what you need to run the cli commands.

. ~/devstack/openrc

See what that does for ya.
___
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] CLI username and password prompt

[Michael Basnight]

On Jul 16, 2013, at 11:19 PM, Jake G. wrote:

> Hi All,
> Every time I type a command from the CLI it requires me to enter a 
> username(--os-username) and password(--os-password) .
> 
> Anyway to prevent having to enter these everytime?

See [1] "Set environment variables"

[1] http://docs.openstack.org/cli/quick-start/content/authenticate.html
___
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 Basnight]

On Jun 14, 2013, at 10:25 AM, Tim Bell  wrote:

> 
> 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.

Agreed :)

> 
> 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.

I'm working on heat integration. That will cover about 90% of the apt/rpm 
mismatch. Then we just need to refactor upgrade a bit, and we will be able to 
support it. 

> 
> 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: 
>> Cc: 
>> 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,  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

___
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 Basnight]

Sent from my digital shackles

On Jun 17, 2013, at 6:23 AM,  wrote:

> On saturday the Reddwarf project has been renamed to Trove ... But ...
> 
> Now trove-integration - https://github.com/openstack/trove-integration/
> - doesn't work anymore (the author updated just some of the links
> related to reddwarf) that's not good.

No it's not. We are aware and we are fixing everything today/tonight. It's our 
dev env too so we are all taking a hit :) we will update the list when things 
get stable. 

> 
> On Fri, 14 Jun 2013 17:25:05 +, Tim Bell  wrote:
>> 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: 
>>> Cc: 
>>> 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,  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
> 

___
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] Reddwarf implementation in Openstack with Red Hat 6

[Michael Basnight]

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,  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

Re: [Openstack] Cinder Multi-Backend Documentation

[Michael Basnight]

+my openstack email. 

I'd love to review. 

Sent from my digital shackles

On Mar 15, 2013, at 8:30 AM, John Griffith  wrote:

> Jerome,
> 
> I would love for you to assign it to yourself :)  You've already done quite a 
> bit of work here with Tempest etc, so as long as hubcap has no objections I 
> say go for it.  Just make sure you put him on the review since he's the 
> master-mind.
> 
> John
> 
> On Fri, Mar 15, 2013 at 8:03 AM, Jérôme Gallard  wrote:
>> Hi John, Michael,
>> 
>> I would like to help for the Cinder documentation.
>> 
>> I have noticed that there is no open bug for the multi-backend documentation.
>> Anne allowed me to open a bug (
>> https://lists.launchpad.net/openstack/msg21938.html ).
>> Is it OK for you if I assign this bug to me or do you have any other
>> plans for the writing of this documentation?
>> 
>> If it's OK for you, I will write this documentation with the help of:
>> https://wiki.openstack.org/wiki/Cinder-multi-backend
>> 
>> Thanks a lot,
>> Jérôme
> 
> ___
> 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] Call for help on Grizzly documentation

[Michael Basnight]

Of course... I spaced. I'd love to review the doc for this.

Sent from my digital shackles

On Mar 15, 2013, at 5:47 AM, "Anne Gentle" 
mailto:a...@openstack.org>> wrote:

Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]

Hey Bas, a DocImpact would have been ideal on that commit message so we could 
already have a doc bug logged. [2]

Thanks,
Anne

1. 
https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines
2. 
https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message




On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard 
mailto:jeronimo...@gmail.com>> wrote:
Hi Anne,

I'm a newbie in the "documentation area" but, I would like to give an help.

I haven't found any documentations (or open bug) regarding the cinder
multi-backend feature (
https://wiki.openstack.org/wiki/Cinder-multi-backend --
https://review.openstack.org/#/c/21815/ ).

Do you know if this documentation is planed to be written?
Can I open a bug for this?

Thanks a lot,
Jérôme

On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle 
mailto:a...@openstack.org>> wrote:
> Hi all,
> You all did great with DocImpact, but now that we're less than a month from
> release, the tiny doc team is facing a long list of doc bugs that won't be
> done by April 4th, many generated by DocImpact flags.
>
> We typically do a "release" of the docs about a month after the actual
> release date, to ensure packages are available and to try to get our doc bug
> backlog to a manageable level.
>
> As you can see from our backlog for operator docs in openstack-manuals [1]
> and API docs in api-site [2], there are over 50 confirmed doc bugs for
> Grizzly operator and admin docs and less than 20 for API docs. With those
> numbers we need all the help we can get.
>
> Please dive in, the patch process is just like code and fully documented.
> [3] We're on IRC in #openstack-doc and can answer any questions you have as
> you go.
>
> Thanks!
> Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps
>
> 1. https://launchpad.net/openstack-manuals/+milestone/grizzly
> 2. https://launchpad.net/openstack-api-site/+milestone/grizzly
> 3. http://wiki.openstack.org/Documentation/HowTo
>
> ___
> 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] [openstack-dev] Optionally force instances to "stay put" on resize

[Michael Basnight]

On Feb 15, 2013, at 9:35 PM, Michael J Fork wrote:

> Adding general and operators for additional feedback.
> 
> Michael J Fork/Rochester/IBM wrote on 02/15/2013 10:59:46 AM:
> 
> > From: Michael J Fork/Rochester/IBM
> > To: openstack-...@lists.openstack.org, 
> > Date: 02/15/2013 10:59 AM
> > Subject: Optionally force instances to "stay put" on resize
> > 
> > The patch for the configurable-resize-placement blueprint (https://
> > blueprints.launchpad.net/nova/+spec/configurable-resize-placement) 
> > has generated a discussion on the review boards and needed to be 
> > brought to the mailing list for broader feedback.
> > 
> > tl;dr would others find useful the addition of a new config option 
> > "resize_to_same_host" with values "allow", "require", "forbid" that 
> > deprecates "allow_resize_to_same_host" (functionality equivalent to 
> > "allow" and "forbid" in "resize_to_same_host")?  Existing use cases 
> > and default behaviors are retained unchanged.  The new use case is 
> > "resize_to_same_host = require" retains the exact same external API 
> > sematics and would make it such that no user actions can cause a VM 
> > migration (and the network traffic with it).  An administrator can 
> > still perform a manual migration that would allow a subsequent 
> > resize to succeed.  This patch would be most useful in environments 
> > with 1GbE or with large ephemeral disks. 
> > 
> > Blueprint  Description
> > 
> > > Currently OpenStack has a boolean "allow_resize_to_same_host" 
> > > config option that constrains
> > > placement during resize. When this value is false, the 
> > > ignore_hosts option is passed to the scheduler. 
> > > When this value is true, no options are passed to the scheduler 
> > > and the current host can be
> > > considered. In some use cases - e.g. PowerVM - a third option of 
> > > "require same host' is desirable.
> > >
> > > This blueprint will deprecate the "allow_resize_to_same_host" 
> > > config option and replace it with 
> > > "resize_to_same_host" that supports 3 values - allow, forbid, 
> > > require. Allow is equivalent to true in the
> > > current use case (i.e. not scheduler hint, current host is 
> > > considered), forbid to false in current use case 
> > > (i.e. the ignore_hosts scheduler hint is set), and require forces 
> > > the same host through the use of the
> > > force_hosts scheduler hint.
> > 
> > To avoid incorrectly paraphrasing others, the review comments 
> > against the change are below in their entirety followed by my 
> > comments to those concerns.  The question we are looking to answer -
> > would others find this function useful and / or believe that 
> > OpenStack should have this option?
> > 
> > Comments from https://review.openstack.org/#/c/21139/:
> > 
> > > I still think this is a bad idea. The only reason the flag was 
> > > there in the first place was so we could 
> > > run tempest on devstack in the gate and test resize. Semantically 
> > > this changes the meaning of resize
> > > in a way that I don't think should be done.
> > 
> > > I understand what the patch does, and I even think it appears to 
> > > be functionally correct based on
> > > what the intention appears to be. However, I'm not convinced that 
> > > the option is a useful addition.
> > >
> > > First, it really just doesn't seem in the spirit of OpenStack or 
> > > "cloud" to care this much about where 
> > > the instance goes like this. The existing option was only a hack 
> > > for testing, not something expected 
> > > for admins to care about.
> > >
> > > If this really *is* something admins need to care about, I'd like 
> > > to better understand why. Further, if 
> > > that's the case, I'm not sure a global config option is the right 
> > > way to go about it. I think it may make 
> > > more sense to have this be API driven. I'd like to see some 
> > > thoughts from others on this point."
> > 
> > > "I completely agree with the "spirit of cloud" argument. I further
> > > think that exposing anything via the 
> > > API that would support this (i.e. giving the users control or even
> > > indication of where their instance lands) 
> > > is a dangerous precedent to set.
> > >
> > > I tend to think that this use case is so small and specialized, 
> > > that it belongs in some other sort of policy 
> > > implementation, and definitely not as yet-another-config-option to
> > > be exposed to the admins. That, or in 
> > > some other project entirely :)"
> > 
> > and my response to those concerns:
> > 
> > > I agree this is not an 80% use case, or probably even that popular
> > > in the other 20%, but resize today 
> > > is the only user facing API that can trigger the migration of a VM
> > > to a new machine. In some environments, 
> > > this network traffic is undesirable - especially 1GBe - and may 
> > > want to be explicitly controlled by an 
> > > Administrator. In this implementation, an Admin can still invoke a
> > > migration manually to allow the resize to 
> >

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

[Michael Basnight]

Seems like a good start to a wiki page to me :)

Sent from my digital shackles

On Dec 6, 2012, at 11:27 AM, "Kevin L. Mitchell"  
wrote:

> Honestly, I don't understand your questions; I figured the documentation
> I pointed you to would answer them, and the fact it doesn't suggests
> that you're not asking what I thought you were asking.  Maybe an
> approach from the beginning:
> 
> Nova, Quantum, Glance, Keystone, etc. all have, as components, a REST
> API.  They use the PasteDeploy package to build this API; PasteDeploy
> provides a means of building a WSGI stack (WSGI is the Python Web Server
> Gateway Interface, an interface by which HTTP requests can be presented
> to a Python application; it allows for not only an application, but also
> a set of "middleware", which wraps the application and can provide
> enhancements).
> 
> The various configuration files you reference are used by PasteDeploy to
> construct the WSGI stack for the API; that is, the configuration file
> tells PasteDeploy that the nova-api service is composed of a specified
> controller, wrapped by middleware that implements exception trap
> translation, authentication checks, ratelimit enforcement, etc., all in
> a specific order.  In essence, the configuration file acts sort of like
> code, rather than configuration; it expresses the structure of the final
> application.  (Although configuration can also be expressed in the file,
> we're trying to avoid that, so that we don't mix configuration with
> code.)
> 
> Does that help you some?
> 
> On Thu, 2012-12-06 at 22:29 +0530, Trinath Somanchi wrote:
>> [1] What is the significance of the api-paste.ini file in the
>> configuration of nova/quantum and other modules of ipenstack?
>> 
>> 
>> [2] How do the modules use these API configuration options? How they
>> are used different from normal ".conf" files?
> 
> -- 
> Kevin L. Mitchell 
> 
> 
> ___
> 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] Is reddwarf for OpenStack is dead now?

[Michael Basnight]

Hey guo,

We havent been as straightforward as we should have been in the last
few months. Reddwarf is alive and well, but we have moved the project
off to http://github.com/hub-cap/reddwarf_lite. We have rewritten the
source entirely to _not_ be a fork of nova, and instead treat it like
a black box and interface with it via novaclient and a few extensions
when needed. Feel free to look @ the newer, cleaner, better, superrerr
code at the aforementioned github. We have plans on migrating it back
to the reddwarf repo, and also to a gerrit install when we have a few
free cycles :)

On Mon, Jul 30, 2012 at 10:54 PM, guo lijing  wrote:
> Hi ALL:
>
>  I'm plan to do something for openstack, and I have experience of building a
> database services(MySQL/Mongodb/Redis) over IaaS, so I try to find some
> project like RDS for openstack,
>   but I found the code of reddwarf in github haven't update for two months?
> What happened to reddwarf, is the team of reddwarf decided not going to do
> this project?
>   I'm new guy to openstack, is anyone can tell me about reddwarf?
>
> --
> ---
> Best Regards
> Lijing Guo
> MSN:hua...@hotmail.com
> GTALK: guolij...@gmail.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
>



-- 
Michael Basnight

___
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] Stackato and OPenStack as PAAS

[Michael Basnight]

Hey frans,

There are a few that I can think of. Reddwarf (my project) [1], platform layer 
[2], and heat [3].  They are all a bit different and I encourage u to look 
around. I bet $$ there are more that I've forgotten, which I apoligize in 
advance for :)

Sent from my digital shackles. 

[1] https://github.com/hub-cap/reddwarf_lite
[2] https://github.com/platformlayer/platformlayer
[3] http://heat-api.org/

On Jul 14, 2012, at 8:15 PM, Frans Thamura  wrote:

> hi all
> 
> one of company here setup Stackato on OpenStack and in beta phase
> 
> any idea and comment regarding PAAS implementation in OpenStack
> 
> F
> ___
> 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom

[Michael Basnight]

On Thu, Jul 12, 2012 at 2:56 PM, George Reese
 wrote:
> I don't think Cinder should exist.
>
> Sometimes you have to live with the technical debt because that's the best
> way to preserve the investment your customers have made in your product.
>
> Or if you're very smart, you find a way to refactor that technical debt
> invisibly to customers.
>
> But you don't make the customer carry the burden of your refactoring
> technical debt.

I hate to fan the fire, but what would happened in cassandra if they
_never_ updated their data structures. Or hadoop, or any other open
source project like that. I understand where you are coming from, but
i would like to find an example of a project thats _never_ updated
their datastore or caused some sort of migration, be it configuration
or data based. I _do_ feel we should roll this migration in the least
painful way possible though.

___
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

[Michael Basnight]

On Thu, Jul 12, 2012 at 2:38 PM, Vishvananda Ishaya
 wrote:
>
> On Jul 12, 2012, at 11:48 AM, Christopher B Ferris wrote:
>
>> This level of response is unnecessary.
>>
>> That said, the perspectives which influenced the decision seemed somewhat 
>> weighted to the development community. I could be wrong, but I did not see 
>> much input from the operations community as to the impact.
>
> Agreed, I'm a developer, so I'm clearly biased towards what is easier for 
> developers. It will be a significant effort to have to maintain the 
> nova-volume code, so I want to be sure it is necessary. End users really 
> shouldn't care about this, so the other community members who are impacted 
> are operators.
>
> I really would like more feedback on how painful it will be for operators if 
> we force them to migrate. We have one clear response from Chuck, which is 
> very helpful. Is there anyone else out there running nova-volume that would 
> prefer to keep it when they move to folsom?

Us reddwarfers are running a grunch of nova volumes in multiple DCs.
While the developer in me says lets go w/ option 1, the
release/operator in me says lets wait to do this on a formal release
(#2?). It seems like we are too far gone in the Folsom release to do
this w/o people having to scramble. Everyone will have to eventually
migrate from old to new, and while i understand that there will be a
clear path to do this, and its going to be painful for some companies.
If we rip things out during Grizzly, it will at least give companies
that are not rolling on trunk the ability to decide when to migrate.
If you do it in Folsom, some companies who are depending on (or
wanting) landed features, but may not be able to do this migration,
could suffer. At least now deferring to El Oso will give companies
time to brace themselves, and successfully migrate to Folsom w/o any
major issues. In general it makes sense to do sweeping changes between
major releases, communicated at the beginning of a release cycle
rather than in the middle, to give operators/companies a decision to
upgrade if they want the features vs stay on old if they dont want to
migrate. At the end of the day, openstack depends on operators to
function. Id rather piss of us developers than piss off the people
that run the infrastructure we create!

That being said, im not worried about the migration, given that its
just a datastore/service/package/installation based migration. We will
likely roll to cinder much sooner than the Grizzly release, assuming
everything is stable (which im sure it will be). :)

___
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] Downstream handling of extensions

[Michael Basnight]

On Jun 14, 2012, at 1:09 PM, Glen Campbell  wrote:

> Two reasons:
> 
> 1. Because there's existing bindings :) None of us are very strong Python 
> developers, and it gives us a chance to get through the existing code and 
> learn from the pros
> 2. Because there's only existing bindings for OpenStack stuff; not for 
> (Rackspace-specific services) CloudDns, CloudDatabases, etc.

Cloud db has a python binding based on the nova client as well. 
http://github.com/hub-cap/python-reddwarfclient
___
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 does everyone build OpenStack disk images?

[Michael Basnight]

In reddwarf for development we use Ubuntu-vm-builder. It works like a charm for 
creating qcow2 images. 

Sent from my digital shackles. 

On Apr 25, 2012, at 8:14 PM, Justin Santa Barbara  wrote:

> How does everyone build OpenStack disk images?  The official documentation 
> describes a manual process (boot VM with ISO), which is sub-optimal in terms 
> of repeatability / automation / etc.  I'm hoping we can do better!
> 
> I posted how I do it on my blog, here: 
> http://blog.justinsb.com/blog/2012/04/25/creating-an-openstack-image/
> 
> Please let me know the many ways in which I'm doing it wrong :-) 
> 
> I'm thinking we can have a discussion here, and then I can then compile the 
> responses into a wiki page and/or a nice script...
> 
> Justin
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Compute/network/volume locality

[Michael Basnight]

Is there a concept of locality in Essex? For example if I stand up a cab that 
connects to a certain volume store, and has a particular network range/vlan, 
and later set up a second "pod" or "cell" and have it be mostly independent 
from the first cab. It seems zone-esque but I'm not sure of the state of zones 
in Essex or if there even is one. I assume some of this will be built out in 
Folsom, but id like to make sure it covers my use case. 

Sent from my digital shackles. 
___
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] Metadata and File Injection (code summit session?)

[Michael Basnight]

On Apr 10, 2012, at 6:19 PM, Angus Salkeld wrote:

> On 10/04/12 15:36 -0700, Justin Santa Barbara wrote:
>>> 
>>> The immediate use case I have in mind is to support this:
>>> http://wiki.openstack.org/**PackageConfigForNova.
>>>   That design requires periodic checkins between an instance agent and a
>>> nova driver.  It certainly /could/ be implemented using ssh, but I
>>> originally wrote the design imagining there was a ready-made, standard
>>> communication service, and I still think it would be convenient.
>>> 
>> 
>> My concern with that proposal is that it starts simple enough, but then
>> when you want to know e.g. "was the package installed successfully? is the
>> service healthy?" then you need more and more complexity i.e. you end up
>> with PlatformLayer, RedDwarf, Heat, Puppet, Chef or Juju.  So putting a
>> small piece of the required functionality into nova doesn't address your
>> actual use case, which is "I want configured machines, not just the stock
>> images".  It's probably easier to put that logic into your management
>> system of choice, so nova shouldn't do it.  Am I off base here?
> 
> Yea, that seem odd. Isn't that what your tool above + cloud-init is for?
> Looks like a layering violation of some kind.

I know im a bit late to the party but i totally agree with Justin. This kind of 
stuff tends to bleed into Platform related tasks, not something that an IaaS 
service like nova would/should perform. Reddwarf gets around it by having a 
small python guest installed on the VM. It currently uses a rabbit cluster for 
communication. Be forewarned, Im not saying that rabbit is the ideal 
communication channel for this job! We have looked into xmpp and metadata svc 
if it can meet our needs. We've talked about guests and communication for the 
last 3 summits and i guess we might be doing the same again this time :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

Re: [Openstack] Keystone database (using latest devstack)

[Michael Basnight]

So disregarding the talk of optimization (much smarter people than i can argue 
that), is what you guys need as simple as listing the roles for a user? 
Keystone itself provides the curl stmt below. Seems very easy to add into 
keystone client if this is all you need.

http://localhost:35357/v2.0/users/UserID/roleRefs

(where for me UserID is f4d42fa3fb9946d084299d3e867bda41 in my devstack install 
for admin)

returning something like below.

{
"roles": [
{
"id": 
"roleId=e6b1d3ee035d4f50a7757a03535d959b&userId=f4d42fa3fb9946d084299d3e867bda41&tenantId=885883dd827d4c90a3740562d7a3630b",
 
"roleId": "e6b1d3ee035d4f50a7757a03535d959b", 
"tenantId": "885883dd827d4c90a3740562d7a3630b", 
"userId": "f4d42fa3fb9946d084299d3e867bda41"
}, 
{
"id": 
"roleId=c30c5ea15e514caf81ea8dc08be69792&userId=f4d42fa3fb9946d084299d3e867bda41&tenantId=885883dd827d4c90a3740562d7a3630b",
 
"roleId": "c30c5ea15e514caf81ea8dc08be69792", 
"tenantId": "885883dd827d4c90a3740562d7a3630b", 
"userId": "f4d42fa3fb9946d084299d3e867bda41"
}, 
{
"id": 
"roleId=1fd81b77f7f64b97b053986ec3004c70&userId=f4d42fa3fb9946d084299d3e867bda41&tenantId=885883dd827d4c90a3740562d7a3630b",
 
"roleId": "1fd81b77f7f64b97b053986ec3004c70", 
"tenantId": "885883dd827d4c90a3740562d7a3630b", 
"userId": "f4d42fa3fb9946d084299d3e867bda41"
}, 
{
"id": 
"roleId=c30c5ea15e514caf81ea8dc08be69792&userId=f4d42fa3fb9946d084299d3e867bda41&tenantId=b8504cc7c5a24b8b80f05065a80abf36",
 
"roleId": "c30c5ea15e514caf81ea8dc08be69792", 
"tenantId": "b8504cc7c5a24b8b80f05065a80abf36", 
"userId": "f4d42fa3fb9946d084299d3e867bda41"
}
]
}

On Mar 8, 2012, at 7:48 PM, Jason Hedden wrote:

> 
> 
> On Mar 8, 2012, at 6:12 PM, Andy Smith  wrote:
> 
>> 
>> I came across this while trying to list the roles assigned to users, which I 
>> still don't know how to do via the keystone client utility. Is this even 
>> possible?
>> 
>> Well, to clarify that statement a bit, roles exist on user-tenant pairs, so 
>> you would list the roles for a user-tenant pair.
> 
> How?  I wasn't able to find a way using the keystone client tools.
> 
> Thanks, 
> Jason
> ___
> 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] What's the web server used in the Nova API server?

[Michael Basnight]

Just curious, whats the reason we went with rolling our own instead of using 
something like nginx/apache2/etc w/ mod_wsgi?
 
On Jan 16, 2012, at 2:14 AM, Thierry Carrez wrote:

> Joe Smithian wrote:
>> I browsed the openStack documentation but couldn't find information
>> about the Nova API server.
>> What's the web server used in the Nova API server?
>> Can we use a different web server  such as Apache or Tomcat?
>> 
>> I'd appreciate your comments.
> 
> Nova uses Python eventlet WSGI servers.
> You can't directly use a different web server, though you can certainly
> place Nova API servers behind some other server.
> 
> -- 
> 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

Re: [Openstack] br100 ip assigned problem

[Michael Basnight]

I typically go in to the db and delete the ips I don't need. The cidr mapping 
will insert all the ips in that range, so go clean them out in fixed_ips in the 
db.

Sent from my iPhone

On Sep 27, 2011, at 1:08 AM, "DeadSun" 
mailto:mwjpi...@gmail.com>> wrote:

Hi, erveryone:

I used FLATDHCP network. And I set br100 on eth0 only. The ip is 
192.168.200.20. Then I assign the fixed_ips range 
"192.168.200.0/24".
But when nova-network restarted, br100 is assigned to 192.168.200.1. This is 
not what I want.

Dose anyone can help me?

2011.3 (2011.3-nova-milestone-tarball:tarmac-20110922115702-k9nkvxqzhj130av2)

--
非淡薄无以明志，非宁静无以致远
___
Mailing list:  
https://launchpad.net/~openstack
Post to :  
openstack@lists.launchpad.net
Unsubscribe :  
https://launchpad.net/~openstack
More help   :  
https://help.launchpad.net/ListHelp
This email may include confidential information. If you received it in error, 
please delete it.
___
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] Database replacement?

[Michael Basnight]

On Sep 24, 2011, at 12:57 PM, "Brian Lamar"  wrote:

> No plans that I'm aware of, there is a Database-as-a-Service project called 
> 'Red Dwarf' which might fit this bill however. I honestly haven't looked too 
> much into it.

Hi, im a developer on the database as a service project. The reddwarf project 
is aimed at deploying MySQL (and more databases to come) in a virtual 
environment. It uses nova to deploy the virtual MySQL instances. It is not 
related to the database replacement issue.
This email may include confidential information. If you received it in error, 
please delete it.


___
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] High availability in openstack?

[Michael Basnight]

Ed and i are on the same team and we are also working on a reaper, using the 
databases instance table state and notifications. If enough of the community is 
behind the idea we can push it upstream. Knowing what to reap can be tricky tho.

Sent from my iPhone

On Aug 18, 2011, at 8:11 PM, "Joshua Harlow" 
mailto:harlo...@yahoo-inc.com>> wrote:

Thanks,

It was along the lines of what I was thinking.

If messages are made persistent, which I hope is planned, or made a 
configuration option what would be the effects of them not being made 
persistent.

Right now if a message is lost, it seems the DB/other nodes are left in a bad 
state, is there any plan to have a “reaper” python object that will reap this 
bad data/instances

On 8/18/11 4:54 PM, "Edward "koko" Konetzko" 
>
 wrote:

On 08/16/2011 04:50 PM, Joshua Harlow wrote:
> Are there any good documentations on making openstack fault tolerant or
> exactly how it will handle failures?
>
> Like say the mq server dies, can another mq server take over. Similar
> with the database (mysql replication?)
>
> Seems like having that kind of information for corporate users would be
> nice, at least a recommended “guide”.
>
> -Josh
>
>
>
> ___
> Mailing list:  
> https://launchpad.net/~openstack
> Post to :  
> openstack@lists.launchpad.net
> Unsubscribe :  
> https://launchpad.net/~openstack
> More help   :  
> https://help.launchpad.net/ListHelp

Josh

I have a very bare bones start of a doc on making parts of Nova HA.  The
problem is this document is no where near ready for release as I am
probably the only person who can understand it.  I will try to point you
in the right direction on things I have done that work pretty well.

Rabbitmq
http://www.rabbitmq.com/pacemaker.html

Right now in the version of Nova the team I am working with nothing is
marked 'persistent'. Right now in this use case if a node fails rabbitmq
moves over and all the managers reconnect with no issues but all in
flight messages are lost.  Maybe someone here can clarify on the
direction of this.  I we are using Ubuntu 10.04 and the version of
Rabbitmq in that release does not have the pacemaker scripts, I just
pulled the current package from rabbitmq.com apt repo 
after that the
pacemaker setup worked perfect.

MySQL
For MySQL I just did a simple setup using DRDB to replicate
/var/lib/mysql and setup corosync/pacemaker to manage all the MySQL
resources between two nodes.  Again with this situation in failover I
had no issues with clients reconnecting to the vip.

I hope this points you in the right direction, I know its not exactly
what you wanted.  Maybe next week I can clean up my documentation and
send it out to the list.

Edward Konetzko

___
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
This email may include confidential information. If you received it in error, 
please delete it.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp