Re: [Openstack] Nova RC-1 Bugs

[Anne Gentle]

You are welcome to triage incoming doc bugs.

Please realize there are less than 10 active doc contributors so
finding more contributors is just as important as finding bugs.

I'd encourage you to both log and fix doc bugs especially at the stage
we're at in the release in hopes of having the highest priority bugs
fixed in time for the release.

Thanks,
Anne

On Thu, Mar 8, 2012 at 2:17 AM, i3D.net - Tristan van Bokkem
 wrote:
> +1 I've made several comments in the Diablo docs of the problems and
> solutions I have found while deploying. Some made it to a change in the
> docs, some didn't. I would like to see the docs being checked before the
> release of essex as failures in the guides are very time consuming and
> frustrating.
>
> Tristan van Bokkem
>
> Sent from my iPhone
>
> On 8 mrt. 2012, at 03:17, "Andrew Clay Shafer"  wrote:
>
> +1
>
> On Wed, Mar 7, 2012 at 7:59 PM, Alexey Eromenko  wrote:
>>
>> There are several blocker bugs in manuals. (they prevent new users
>> from installing or configuring OpenStack)
>>
>> But I doubt they are marked as such.
>>
>> What to do ?
>> Can I up priority for docs on L-pad, if a broken docs prevent new
>> users from configuring OpenStack ?
>>
>> --
>> -Alexey Eromenko "Technologov"
>>
>> ___
>> 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

[Openstack] Doc Day actions

[Anne Gentle]

Hi all -
Thanks everyone for the hard work at the Essex Doc Day this week! We
still have nearly 20 doc reviews in the queue :
https://review.openstack.org/#q,status:open+project:openstack/openstack-manuals,n,z
so please review and see if your favorite doc bug was fixed!

Several discussions came up at Doc Day that I wanted to bring to the
larger group. Feel free to comment as you see fit.

_Information architecture_
On further investigation, I believe the Image Admin manual and
Identity Admin manual can go away and the information be absorbed in
to the Compute Admin manual and the Object Storage admin manual as
they are supporting projects for the Compute and Storage end-goals.
These documents were sourced from RST dev docs, aren't well
maintained, and I think it's best to move towards a focus on Compute
and Storage admin manuals based on web analytics and available
resources.
Anthony has an outline at http://etherpad.openstack.org/drs6dPNF4p for
a User Guide that doesn't current exist and a Compute Administration
Guide that is similar to the current guide but contains more
information and a more logical flow.

Actions:
- Anne to remove the Identity Admin manual and Image Admin manual so
they will not be separate documents for the Essex release.
- Anne to place the relevant content into the Compute Admin manual.
- All: review outlines at http://etherpad.openstack.org/drs6dPNF4p and
comment inline
- Anne to determine source (or lack of) of each "topic" in Anthony's
admin manual outline.

_Doc accuracy_
Jesse voices a concern about the overhead XML brings to quick doc
fixes and when on boarding developers asking them to use a special
tool outside of their workflow like Oxygen. Inaccuracies that his team
is most likely to have the knowledge to spot and correct are difficult
to fix. Launchpad for doc bugs is not a favorite toolset.
Actions:
- Log doc bugs, review fixes to those bugs.

_Doc workflows_
Jesse Andrews and members of the Rackspace Cloud Builders (RCB) team
voiced a concern about new authoring and maintenance tasks, he senses
that the XML requirement is too hefty for developer contributors. He
would rather have devs write all the documents. Anne thinks that the
distro contributors are more likely to use DocBook and Jay Pipes
agreed.

Here are some specific authoring requirements and review requirements
for Python devs, which I'll try to describe in detail here. Please
update as you see fit:
As a Python dev, I want to author in command-line tools already in my
Python toolset that are already installed and familiar to me so that
my workflow is not interrupted.
As a Python dev, I want to locally build and view output from the
command line just as it appears on the docs site including the landing
pages so that I can see the changes due to my edits.
As a Python dev, I want to review other author's work without viewing
XML source so that the changes in the patch are easily discernible.

Here are some specific authoring requirements for doc contributors.

As a doc contributor, I want to review other contributor's work as
HTML output with markup so that I can see their changes quickly rather
than building locally.
As a translator, I want to have document strings presented in tools
that are familiar to me with changes being easy to discern.
As a translator, I want a known frozen release set of English
documents to be translated to another language so that I can work on a
document with good faith that the content remains accurate through the
translation process.
As a doc contributor, I have needs for markup that ensure numbered
list continues numbering even when code samples or program listings
are part of the list item.
As a doc contributor, I have certain document conventions that need
output to be distinguished as described in
http://wiki.openstack.org/Documentation/Conventions.
As a doc contributor, I need to ignore whitespace and XML formatting
so that doc reviews are easier to complete regardless of the authoring
tool.
There are also audience needs.
As a document commenter, I need to understand the chunking of the
content so I know what pice of content (page or section) to place a
comment on.

Actions:
- Anne to create a blueprint for openstack-manuals to be discussed at
the Summit specifically to address the reviewing difficulties.
- Jesse and team to scope work on an RST-only workflow for developers,
using one small deliverable as a test case.

_Doc tool chain source_
Matt Stephenson, an attendee at the Doc Day wants to see how he could
contribute to the Maven plugin.
Action:
- Joe Savak to inform OpenStack community of timeline for
contributions to the Maven plugin.

I really appreciate all the hard work on docs this release. Let's keep
the energy going for the next three weeks.
Warmly,
Anne

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://hel

Re: [Openstack] [RC BUGS] Call for Help: openstack-manuals

[Anne Gentle]

Answers below.

Also please note my email earlier today where I want to bring all
Identity and Image admin instructions into the Compute and Storage
manuals.

Thanks for the attention to details.
Anne

On Thu, Mar 8, 2012 at 5:42 PM, Alexey Eromenko  wrote:
> Hi,
>
> After contributing "Installation on Debian" section, I have removed
> the strong link between Ubuntu and the official O-S docs.
> (wish: https://bugs.launchpad.net/openstack-manuals/+bug/943792)
>
> I would like to request co-operation to better check those manuals,
> report bugs and fix them.
> Currently, both nova and keystone docs are broken, and I need help
> (knowledge) to fix them.
>
> Critical Problems:
> 1. legacy auth is still used in nova docs
> https://bugs.launchpad.net/openstack-manuals/+bug/941711

Please review this patch for the bug you mention:
https://review.openstack.org/4822


> 2. many keystone commands from official openstack-manual (keystone-trunk) 
> fail.
> Such as:
> # keystone-manage tenant add admin
> (can't find bug #, but I remember there was one)

Yes, please help with keystone docs, the command line help should help
you figure out the equivalent new command.
>
> Problem is: We don't have much time, and I'm would like to contibute
> to ensure docs-for-Essex will be production quality on release date.
> Since those bugs will prevent new users from installing openstack, I
> consider them critical.
> --
> -Alexey Eromenko "Technologov"
>
> ___
> 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] [RC BUGS] Call for Help: openstack-manuals

[Anne Gentle]

Yes I had hoped to have a merge request today but I should be able to
do it tonight or tomorrow.

The Keystone info will still be inaccurate until it's re-written based
on the new implementation.

Anne

On Thu, Mar 8, 2012 at 7:05 PM, Alexey Eromenko  wrote:
> On Fri, Mar 9, 2012 at 2:28 AM, Anne Gentle  wrote:
>> Answers below.
>>
>> Also please note my email earlier today where I want to bring all
>> Identity and Image admin instructions into the Compute and Storage
>> manuals.
>
> Fine. Those are pretty short manuals, just 40-50 pages each.
> Also logically, they fit great in nova and swift guides.
> But is this transition planned for Essex ?
>
> --
> -Alexey Eromenko "Technologov"
>
> ___
> 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] Google Summer of Code-2012

[Anne Gentle]

Thanks mentors for your ideas. I've compiled them into an ideas page
that still needs more details including where the code lives and
prerequisite knowledge so the students can make good decisions.

http://wiki.openstack.org/GSoC2012/Ideas

Russell and I are meeting tomorrow morning to complete the application.

Please fill in the details in the above page prior to about 24 hours from now.

Let's make it happen!

Anne

On Thu, Mar 8, 2012 at 8:38 AM, Russell Bryant  wrote:
> On 03/06/2012 03:52 AM, Thierry Carrez wrote:
>> Russell Bryant wrote:
>>> On 03/05/2012 02:17 PM, Anne Gentle wrote:
>>>> Okay, looks like the Mentoring organization application deadline is
>>>> this Friday, March 9th.
>>>>
>>>> What needs to be done in time to make this important deadline and how
>>>> can I help?
>>>
>>> We need some minimum number of mentors to volunteer to make the overhead
>>> of participating in the program worthwhile.  That number is subjective
>>> ... I'd say it would be nice to have at least 4 or 5 mentors volunteer.
>>
>> Yes, I think if we don't have at least 4 mentors and ~10 proposed ideas
>> by Thursday morning, it's not worth rushing our application in.
>
> 6 mentors have signed up, so I think we should proceed.
>
> Anne and I can work on the application.  The other thing that should be
> done is updating the existing wiki page to be the ideas page for
> interested students.  Feel free to add any information that you think
> interested students should know about working with OpenStack.
>
> --
> Russell Bryant
>
> ___
> 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 with Xen

[Anne Gentle]

I would also ask Ewan to ensure his patch with the Xen chapter to land
for openstack-manuals.
Thanks
Anne

On Sat, Mar 10, 2012 at 5:28 AM, Thomas Goirand  wrote:
> On 03/10/2012 06:10 PM, Armando M. wrote:
>> That's great! if you find gaps, it's a wiki...feel free to fill them up
>> or ask the authors to do so. You are in a great position due to your
>> packaging experience, and your input would be very valuable.
>
> This is on my TODO, when I will consider that I'm ready myself with
> Openstack + XCP, which isn't the case yet. For the moment, I write notes
> in README.Debian files.
>
> Thomas
>
> ___
> 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] [Docs] Gaps still to fill for Essex

[Anne Gentle]

Hi all -
I've been working through the outline that Anthony Young suggested at
last week's Doc Day, and still finding gaps. I'd like to fill these
specifically prior to Essex, so I wondered if a general call for help
to the doc-core list and the larger mailing list would render some
good contributions! If you can write a web page (or know of an
existing one) about one of these topics, please add it to the docs
through the code submission process. I've logged a doc bug for each of
these.

Overview of RBAC model and policy.json configuration
https://bugs.launchpad.net/openstack-manuals/+bug/953129

LDAP with Keystone
https://bugs.launchpad.net/openstack-manuals/+bug/953132

Configuring nova-api
https://bugs.launchpad.net/openstack-manuals/+bug/953134

Configuring the ec2 compatibility api for Compute
https://bugs.launchpad.net/openstack-manuals/+bug/953137

Object store configuration for Compute
https://bugs.launchpad.net/openstack-manuals/+bug/953138

Metadata configuration for Compute
https://bugs.launchpad.net/openstack-manuals/+bug/953148

Network configuration - Linux bridging, OVS, Multi-nic
https://bugs.launchpad.net/openstack-manuals/+bug/953151

If you can work on these specific gaps, please assign yourself to a
bug and get to doccing.

Thanks,
Anne

___
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 Installation Woes - Need re-assurance and help.

[Anne Gentle]

Hi Shep and others -
A couple of questions to enhance my understanding while I walk through this
for the install doc.

Service Tenant - do you create just one service tenant to enclose all the
service users?

Glance Service User - do you create a Nova Service User and a Swift Service
User also?

files/default_catalog.templates - are your commands updating the template
or a database? It this is a point of confusion. I guess I have to also add:
[catalog]
driver = keystone.catalog.backends.sql.Catalog

to keystone.conf in order to use a database backend for my service catalog?
Thanks for improving my mind map.

Anne

On Tue, Mar 13, 2012 at 8:59 PM, Justin Shepherd wrote:

>  Sent this to kevin earlier, thought i would throw it out to the list..
> here are the steps i take to get a working keystone and glance on
> Ubuntu-12.04 using the ubuntu packages.
>
>  http://paste.openstack.org/show/9101/
>
>  These steps produce a working keystone and glance.. not 100% sure they
> are the most efficient steps, would be curious to hear from others if there
> is a better way.
>
>  --shep
>
>
>  On Mar 13, 2012, at 5:41 PM, Adam Gandelman wrote:
>
>  On 03/13/2012 01:53 PM, Kevin Jackson wrote:
>
> Whilst OpenStack is being developed, a lot of people's entry into
> OpenStack is through deb packages (or  in here>) - therefore Ubuntu becomes unofficial (but vocal) PR to
> OpenStack.  If the Ubuntu debs don't install, it becomes Plan B to install
> from somewhere else - even if that somewhere else is openstack.org.  When
> we view the pages of http://www.ubuntu.com/cloud there is little doubt
> that OpenStack is a 1st class citizen (Best-of-breed cloud infrastructure
> is built into every copy of Ubuntu).
>
>
> Kevin-
>
> As someone who helps maintain the Ubuntu packages, I'm curious to know
> when/what/where the problems you've hit installing packages. Do/did bug #s
> exist?  Can you please file bugs when you hit them?  We've been making an
> extra effort to ensure that the Openstack packages on archive.ubuntu.comare 
> *at least* installable without error at any given time.  Packaging bugs
> have slipped through into our weekly uploads, but we've been either
> catching them early or responding to any new relevant bug reports, and
> doing point uploads with fixes ASAP so things are installable until the
> next weekly upload.
>
> I ask  anyone that is running into packaging problems: Please file bugs
> against the Ubuntu packages if you find they are failing to install.  They
> *will* get fixed!
>
>
> Adam
>
>  ___
> 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] Removal of VSA Code

[Anne Gentle]

Without install and config docs it is too difficult to ask testers to try it. 

My docs request of this particular volume extension was in the diablo release 
but is still needed in Essex. Let's start with a docs merge request before 
asking people to test it. 

Let me know if you need an orientation to doc tools, the merge process itself 
is just like the code.

Warmly,
Anne Gentle
Content Stacker
a...@openstack.org


On Mar 15, 2012, at 12:09 PM, Vladimir Popovski  
wrote:

> If there is anything broken in Essex due to this code, please let me know
> and we will take a look/fix it.
> 
> The main reason why we would like to have it in place - to make developers
> aware that there is somebody relying on particular functionality and/or
> particular function/module. Otherwise we will be in a constant merge
> conflict and every time we will need to manually review almost any change
> that is applied to the trunk and check if it anyhow affects/breaks it.
> 
> Thanks,
> -Vladimir
> 
> 
> -Original Message-
> From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com]
> Sent: Thursday, March 15, 2012 9:53 AM
> To: Vladimir Popovski
> Cc: Vishvananda Ishaya; openstack@lists.launchpad.net
> Subject: Re: [Openstack] Removal of VSA Code
> 
> On Thu, 2012-03-15 at 09:02 -0700, Vladimir Popovski wrote:
>> I was not aware of any issue with VSA code in diablo/stable (or at
>> least major issues).
> 
> I'll point out that the code we're concerned about is the code in trunk, not
> the code in diablo/stable.  There have been substantial changes to the code
> since diablo was released, which has resulted in bitrot in the VSA code and
> the attendant breakages to which Vish is referring.
> --
> 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] "nova zone" and "availability_zone"

[Anne Gentle]

I believe we have doc tools now that would enable a shared glossary for all
documents. Let me investigate and report back to the list.

Anne

On Tue, Mar 20, 2012 at 6:21 AM, Tim Bell  wrote:

> ** **
>
> 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.htmlwhich
>  defines some concepts.
> 
>
> ** **
>
> From http://wiki.openstack.org/Glossary, there is a pointer to
> http://cloudglossary.com/ but the openstack terms are not in there.
>
> ** **
>
> There is also
> http://docs.openstack.org/incubation/openstack-network/developer/quantum-api-1.0/content/Glossary.htmlfor
>  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.
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ___
> 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] [keystone] Keystone XSDs?

[Anne Gentle]

Hi Liem,

The WADLs have been moved from the openstack/keystone repo to the
openstack/identity-api repo. Each OpenStack project that has an API has a
separate repo for the API wadls (and docs).

Anne

On Tue, Mar 20, 2012 at 10:59 AM, Nguyen, Liem Manh wrote:

>  Hello stackers,
>
> ** **
>
> I checked out the new Keystone (KSL), and the XSD’s and WADL’s are not
> there anymore…  Do they live somewhere else now?
>
> ** **
>
> Thanks,
>
> Liem
>
> ___
> 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] Please stop the devstack non-sense!

[Anne Gentle]

On Tue, Mar 20, 2012 at 1:57 PM, Michael Pittaro  wrote:

>
> Install and configuration documentation is an area we need to focus
> on more, and it will need much more community involvement to really
> make a difference.  The situation is currently much better than it
> was back in September 2011, so progress _is_ being made.
>
>
+1

Agreed, and Mike you've helped here. We need more documentation on
configuration. Specifically here are some doc bugs anyone with the
knowledge could pick up:


 #953134 Docs need Essex info for configuring
nova-api
 openstack-manuals  6

 #953137 Need docs for Configuring the ec2 compatibility api for Compute in
Essex 
 openstack-manuals  6

 #953138 Need doc update for Essex for configuring Compute's storage
system
 openstack-manuals  10

 #953148 Metadata configuration needs to be documented in
Essex
 openstack-manuals  6

 #953151 Network configuration - Linux bridging, OVS, Multi-nic not well
documented for Essex

Anne
___
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] Installion guide for OpenStack Essex on Ubuntu 12.04

[Anne Gentle]

Great work, Martin! It really does show that an installation can be
completed for a proof of concept quite quickly.

I tested the entire guide, and found I couldn't change the hastexo password
in the keystone_data.sh even if I changed it in the keystone.conf file, not
sure why not. Your instructions are correct, it's just that small changes
are going to have cascading effects. Perhaps you could be more clear about
the re-use of the SERVICE_TOKEN="hastexo" being the same as the
ADMIN_PASSWORD (I changed one but not the other, not realizing the
"hastexo" string was in both places). It is what it is, not much a user can
do about it other than tread carefully.

You should also be more clear about editing the nova.conf file to replace
your 10.42.0.6 IP address with the IP address of the server the user is
installing upon in Step 5 [1]. You also need to restart the nova services
after editing the nova.conf file so that the MySQL config is picked up,
right?

As I mentioned in our IRC chatting, I'd like to see your guide brought into
the community docs site as a quick start, once the "substitute this python
file for that" parts are sorted out through the bug fixes and package
updates we'll hope get in 12.04 in time.

To my eye, it's similar to the CSS OSS Beginner's Guide, but much quicker
start to finish without explanatory text or object storage. So what I'd
like to suggest is that you propose this guide to be added to the OpenStack
docs - it'll help with maintenance and ongoing edits.

I can help you create a "quick start" guide with "Built for OpenStack" logo
and your logo (now available thanks to work from the docs tools team here
at Rackspace, you could be the first one to try it). This would mean
bringing the source into DocBook and the openstack-manuals github
repository. You can keep the CC-By-SA licensing for the document by going
this route, though I do want to hear what other doc contributors think of
this approach. In our conversations, you just said "CC-By-SA" - could you
be more specific about which license you want? We welcome Creative Commons
licensing but doc contributors do want to be able to contribute without
commercial implications.

Any docs-core members care to comment on bringing it in the
openstack-manuals repo if Martin is willing?

Thanks,
Anne

[1]
http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-5-install-and-configur

On Mon, Mar 26, 2012 at 8:50 AM, Martin Gerhard Loschwitz <
martin.loschw...@hastexo.com> wrote:

> Hi folks,
>
> I've written a guide on how to install OpenStack Essex on Ubuntu 12.04.
> It covers the installation and configuration of Keystone, Glance, Nova
> and Horizon. By following this guide, even people that haven't collected
> much OpenStack experience so far should be able to get the virtualization
> environment up and running in a short period of time.
>
> The full document is available from here:
>
> http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin
>
> All feedback and comments are much appreciated -- thanks in advance!
>
> Best regards
> Martin
>
> --
> Martin Gerhard Loschwitz
> Principal Consultant
> hastexo Professional 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
>
___
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] Installion guide for OpenStack Essex on Ubuntu 12.04

[Anne Gentle]

Hi Martin -
More explanation below, thanks for the fixes. They are spot on.

> One python file exchange is gone already, and the other one, as Adam stated, 
> is
> hopefully due for deletion today or tomorrow once the horizon package in 
> Ubuntu
> gets the necessary patch. As soon as the package hits Precise, I will remove
> the wget-part and add a warning instead that people need to use at least the
> version that includes the fix to get the Dashboard working.

Great news, thanks go to the packagers too. I love how this document
could bring these
bugs to light and get them fixed.


> Ahum, I must admit this puzzles me a bit. We have no intention whatsoever to
> force anyone into commercial implications; what we want is that everybody is
> able to use, change and redistribute the file as he/she sees fit. After all,
> that's the idea behind F/OSS, isn't it? I'm a Debian Guy, so i'm anything but
> reluctant to that idea :)

So we do like CC-By-SA if that's the one you really mean. Sometimes
people say "Creative Commons" but then choose a more restrictive
license. The by-nc-sa that the Starter Guide uses is much more
limiting so it tends to have a small group of contributors and I've
heard from a potential contributor that the individual wouldn't be
likely to work on it due to the license. Mostly the docs that live
with the code are Apache2 licensed. Creative Commons is more
meaningful and easy to understand for documentation so I welcome those
licensed works as well in openstack-manuals.

>> Any docs-core members care to comment on bringing it in the 
>> openstack-manuals repo if Martin is willing?
>>
> I'll be most happy to cooperate with whoever is the person in charge for this!

Yeah, I'm the "benevolent dictator" in charge of docs-core. :) Wanted
to see if other smart docs
folks have comments before proceeding.

Appreciate the dialog!
Anne

> Best regards
> Martin
>
> --
> Martin Gerhard Loschwitz
> Chief Brand Officer, Principal Consultant
> hastexo Professional Services
>
> CONFIDENTIALITY NOTICE: This e-mail and/or the accompanying documents
> are privileged and confidential under applicable law. The person who
> receives this message and who is not the addressee, one of his employees
> or an agent entitled to hand it over to the addressee, is informed that
> he may not use, disclose or reproduce the contents thereof. Should you
> have received this e-mail (or any copy thereof) in error, please let us
> know by telephone or e-mail without delay and delete the message from
> your system. Thank you.

___
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] Programming OpenStack Compute API - 1.1 Mistake

[Anne Gentle]

Hi Nicolas -
Glad you like the book! Jacek Artymiak gets all the credit for it, and
he wrote and tested it against TryStack. So for now, it uses old-style
Keystone requests as those will work against TryStack.

TryStack plans an upgrade in April, not to steal thunder or anything
from them, but I'd expect we can do updates to the guide after that.

If you wouldn't mind, could you log a doc bug to track that effort,
basically requesting Auth content updates to go with Keystone
light/redux? Log it in http://bugs.launchpad.net/openstack-manuals.

Thanks,
Anne

On Wed, Mar 28, 2012 at 4:10 AM, Nicolas Odermatt  wrote:
> Hello Anne
>
> I am playing with the OpenStack API on my StackOps environment to get an
> idea of how to use it for scripts to programm some little scripts.
> I read the documentation "Programming OpenStack Compute API - 1.1" and tried
> the code examples but at one specific script the machine threw me an error.
> The mentioned script is found in Chapter "2. The Basics" in the section
> "Using Python to Obtain the Authentication Token". If you copy-paste the
> script in a file, adjust the variables like username, password, etc. and
> then execute the file, you will receive a parse error from python:
>
> "root@nova-controller:~# ./gettoken.py
> {"badRequest": {"message": "Cannot parse auth", "code": "400", "details":
> "Expecting object: line 1 column 43 (char 43)"}}
> Traceback (most recent call last):
>   File "./gettoken.py", line 41, in 
>     apitoken = dd['auth']['token']['id']
> KeyError: 'auth'"
>
> This is due to the fact that line 39 tries to extract the api token from the
> response ['auth']['token']['id'], which rather ought to be
> ['access']['token']['id']
>
> old: apitoken = dd['auth']['token']['id']
> new: apitoken = dd['access']['token']['id']
>
> As you might have noticed you receive an answer, which states "badRequest".
> From former experience with the API, I remembered that this means that there
> is something wrong with the credentials provided to keystone. I checked the
> params variable and realized that there was no information about the
> tenantid. Therefore I edited the line like this:
>
> old:params = '{"passwordCredentials":{"username":osuser,
> "password":ospassword}}'
> new: params = '{"auth":{"passwordCredentials":{"username": osuser,
> "password":"ospassword"}, "tenantId":ostenant}}'
>
> After that the script worked like a charm. Could it be that this error only
> occurs on StackOps environments or is it a spelling error?
>
> PS: I learned a lot from the "Programming OpenStack Compute API"
> documentation. Thank you very much for this superb how to!
>
> Best regards,
> Nicolas
>
> --
> Freundliche Grüsse,
> Nicolas Odermatt
>

___
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] [Docs] how are we doing for Essex release?

[Anne Gentle]

Hi all,
I'm still hearing that "the docs are outdated" and would like a gut
check. We are fixing bugs all the time, but the backlog of confirmed
doc bugs remains over 100. If you are still seeing errors or
omissions, can you please help by reviewing docs and filling in the
gaps?

Here are the yet-unfilled areas that I consider high priority for Essex:

1. Image management - a portion of this chapter is shared with the
book sourced in the Launchpad openstackbook project, and looking at
the project source, that hasn't been updated recently. There are
several doc bugs to fix here:
https://bugs.launchpad.net/openstack-manuals/+bug/967101
https://bugs.launchpad.net/openstack-manuals/+bug/957618
https://bugs.launchpad.net/openstack-manuals/+bug/967094
If anyone has a nice set of instructions on making images and
uploading them we could use them.

2. Migration from Diablo to Essex: I've logged
https://bugs.launchpad.net/openstack-manuals/+bug/967402 and asked
Razique to write this section as he did a great job with the Cactus to
Diablo topic.

3. RBAC and policy.json - Joshua, any interest?
https://bugs.launchpad.net/openstack-manuals/+bug/953129

4. Metadata configuration -
https://bugs.launchpad.net/openstack-manuals/+bug/953148

5. EC2 compatibility - https://bugs.launchpad.net/openstack-manuals/+bug/953137

6. Network configuration -
https://bugs.launchpad.net/openstack-manuals/+bug/953151

Thanks all for the updates so far. I welcome the work ethic folks have
brought to the doc!

Anne

___
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] [Docs] Glossary (was "nova zone" and "availability_zone")

[Anne Gentle]

All,

I've added a doc review for a glossary at
https://review.openstack.org/#change,5847. It came from the Repose
project, and is Apache 2 licensed, so I guess it makes sense to edit
and bring it into the OpenStack umbrella.

I haven't yet added zones or availability zones to the glossary, nor
have I incorporated it further into a guide. There is also a method to
have definitions as pop-ups within other pages. These would be "next
steps" for glossary work. Hint: glossary work is not my favorite so
anyone can be owner of this. :)

I'd like review for the current definitions as well as suggestions for
additions (and definitions) before investing more effort into
incorporation, so feel free to take a look and give feedback.

Thanks,
Anne

On Tue, Mar 20, 2012 at 6:21 AM, Tim Bell  wrote:
>
>
> 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
> which defines some concepts.
>
>
>
> From http://wiki.openstack.org/Glossary, there is a pointer to
> http://cloudglossary.com/ but the openstack terms are not in there.
>
>
>
> There is also
> 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.
>
>
>
>
>
>
>
>
>
>
> ___
> 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] [Doc] Nova options changes and documentation

[Anne Gentle]

Hi Docs Core team and others,
David Kranz has identified changes to the nova.conf configuration options
in the attached .diff file. They directly affect the configuration chapter
for the Compute Admin manual as well as the networking chapter.

I have also gone through all the possible flags and created this list:
http://etherpad.openstack.org/newflagsessex indicate what are new in Essex.

I realize this is a lot of work and I'd like ideas for how to track the doc
work for all these changes. My sense is that many are already logged as doc
bugs so possibly I just log more bugs based on groups of flags.

So, no my question. Should I log new doc bugs for each these?

logging options changes
networking options changes
credentials options changes
monkey patching for eventlet/greenlet options
S3 SSL options
Netapp options
Kombu options
zone options: default Scheduler zone option, fill first option, least cost
new images and Glance options

There are already doc bugs logged for these options:
nova api options (https://bugs.launchpad.net/openstack-manuals/+bug/705070)
LDAP options changes (
https://bugs.launchpad.net/openstack-manuals/+bug/953132)
Linux bridging options (
https://bugs.launchpad.net/openstack-manuals/+bug/953151)
policy options (https://bugs.launchpad.net/openstack-manuals/+bug/922147)

How else can we parcel out the doc work and track it? Open to any and all
ideas here.

Thanks,
Anne


diablo-essex-flags-diff
Description: Binary data
___
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] EC2 metadata

[Anne Gentle]

We really don't have secret wikis that I know of. :)

Though then they'd really be secret!

Anne

On Thu, Mar 29, 2012 at 3:33 PM, Soren Hansen  wrote:
> 29. mar. 2012 00.55 skrev Joshua Harlow :
>> I’ve seen that before. But was wondering if there was any secret other wiki.
>
> There is no secret wiki that I'm aware of.
>
> If you believe the referenced wiki page is out of date, please help update it.
>
> --
> Soren Hansen             | http://linux2go.dk/
> Senior Software Engineer | http://www.cisco.com/
> Ubuntu Developer         | http://www.ubuntu.com/
> OpenStack Developer      | http://www.openstack.org/
>
> ___
> 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] [Doc] Nova options changes and documentation

[Anne Gentle]

Yes. This. More below.

On Fri, Mar 30, 2012 at 4:06 AM, John Garbutt wrote:

> > > How else can we parcel out the doc work and track it? Open to any and
> > > all ideas here.
> >
> > I think a blueprint for the 'Essex Flags' documentation will help track
> it.  We
> > can then link bugs to the blueprint, and update the blueprint with any
> > additional notes or links.
> >
> > I think a single bug for each group of options will probably suffice;
>  there will
> > only be a few people working on this anyways.
>
> Can automate that?
>
> Maybe get Jenkins, when it merges a branch, to raise a doc bug if a new
> flag has been added, or the flag comment or default has changed?
> You might get a few false positives, but that is probably no bad thing.
>

Thanks, John. I know lots of open source projects do this, let's do it.
Monty and gang, I added to the doc automation blueprint on openstack-ci at
https://blueprints.launchpad.net/openstack-ci/+spec/ci-doc-automation.

Important note: I don't want devs to think this is how they throw stuff
over the wall to a "team of doc writers" since we don't have dedicated doc
resources for configuration docs (that I know of, unless there's a secret
wiki, ha!). There's a small group, we're organized and need a list for the
backlog, but need all the people who know about config to help.

Thanks, so glad I can bounce ideas here.
Anne


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

Re: [Openstack] nova-manage required or deprecated for essex?

[Anne Gentle]

Hi Lorin -
My understanding is nova-manage image is not available any longer, but
based on the team meeting on , we are not planning to remove it from docs
since it's just too much work in the timed release timeframe for Essex.

For certain nova-manage image is not available, that's the point behind doc
bug https://bugs.launchpad.net/openstack-manuals/+bug/957618

For Essex, the docs (and admins) still need to use nova-manage commands for:
-network creation
-migrating from deprecated auth to Keystone
-quick status checks on running services (nova-manage service list)
-database sync (migration)
-live migration seems to be using it a bit

Most other admin tasks can be accomplished in other ways and aren't
documented with nova-manage commands.

Let me know if this list of nova-manage commands sounds accurate - Vish,
Joe Heck, Brian Waldon?
Thanks,
Anne

On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein wrote:

> Is nova-manage deprecated in essex, or are there some commands that still
> require nova-manage? I'd like to update the docs accordingly.
>
> Yaguang Tang in this bug <
> https://bugs.launchpad.net/openstack-manuals/+bug/957618> said "nova-manage
> will be deprecated". But I couldn't tell from the context if he was
> referring specifically to "nova-manage image", or to nova-manage in general.
>
> Right now, the docs have about 100 mentions of nova-manage:
>
> [(master) docbkx]$ find . -name '*.xml' | xargs grep "nova-manage"| wc -l
>   98
>
>
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.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
>
>
___
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-manage required or deprecated for essex?

[Anne Gentle]

Woops, meant to paste in a reference to
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-01-31.log

"team meeting on January 31"

derp. :)

Anne

On Mon, Apr 2, 2012 at 9:21 AM, Anne Gentle  wrote:

> Hi Lorin -
> My understanding is nova-manage image is not available any longer, but
> based on the team meeting on , we are not planning to remove it from docs
> since it's just too much work in the timed release timeframe for Essex.
>
> For certain nova-manage image is not available, that's the point behind
> doc bug https://bugs.launchpad.net/openstack-manuals/+bug/957618
>
> For Essex, the docs (and admins) still need to use nova-manage commands
> for:
> -network creation
> -migrating from deprecated auth to Keystone
> -quick status checks on running services (nova-manage service list)
> -database sync (migration)
> -live migration seems to be using it a bit
>
> Most other admin tasks can be accomplished in other ways and aren't
> documented with nova-manage commands.
>
> Let me know if this list of nova-manage commands sounds accurate - Vish,
> Joe Heck, Brian Waldon?
> Thanks,
> Anne
>
> On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein 
> wrote:
>
>> Is nova-manage deprecated in essex, or are there some commands that still
>> require nova-manage? I'd like to update the docs accordingly.
>>
>> Yaguang Tang in this bug <
>> https://bugs.launchpad.net/openstack-manuals/+bug/957618> said "nova-manage
>> will be deprecated". But I couldn't tell from the context if he was
>> referring specifically to "nova-manage image", or to nova-manage in general.
>>
>> Right now, the docs have about 100 mentions of nova-manage:
>>
>> [(master) docbkx]$ find . -name '*.xml' | xargs grep "nova-manage"| wc -l
>>   98
>>
>>
>>
>> Take care,
>>
>> Lorin
>> --
>> Lorin Hochstein
>> Lead Architect - Cloud Services
>> Nimbis Services, Inc.
>> www.nimbisservices.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
>>
>>
>
___
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] Documenting public sites with VM images

[Anne Gentle]

Rackspace Cloud Builders has a nice list at
https://github.com/rackerjoe/oz-image-build of pre-built images.

It would be nice to update the docs with info about that oz-image-build
tool also.

Anne

On Mon, Apr 2, 2012 at 10:11 AM, Lorin Hochstein
wrote:

> All:
>
> I'm working on a doc update on where to download VM images that work with
> OpenStack . So far, I've got sections
> on CirrOS (Scott Moser's test image), Ubuntu and Fedora. Are there any
> other projects out there that have downloadable images that we can point
> users to?
>
>  Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.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
>
>
___
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] [Doc] OpenStack doc web properties

[Anne Gentle]

Hi all -
Wanted to send a note out to let people know I'm listening to the various
difficulties finding accurate docs, and also provide my sense of the scope
of the docs for OpenStack.

I want to have a session at the Design Summit about the blossoming docs
sites but also discuss how to prune and de-dupe docs. Here are all the
"doc" properties - not that I own them all, but that they are locations
where people get info that can go out-of-date. I want to prioritize and
focus docs for the Folsom release and welcome your input. This info is
copied to this Etherpad: http://etherpad.openstack.org/folsomdocsplanning,
feel free to edit and add as you see fit.

__Admin guides__
Where: http://github.com/openstack/openstack-manuals

What:
- docs.openstack.org
- Compute Admin manual
- Object Storage Admin manual
- Supporting projects such as identity and image management are shared
chapters inserted into each.
- Network connectivity (Quantum) Admin manual

Who:
Day-to-day administrators of OpenStack clouds (public and private)

How: Updated through the git/Gerrit review process.

__Install guides__
Where: http://github.com/openstack/openstack-manuals
What: docs.openstack.org Compute Install/Deploy guide with identity, image
management, dashboard as chapters.
How: Updated through the git/Gerrit review process.

Where: http://launchpad.net/openstackbook
What: docs.openstack.org Ubuntu release-based OpenStack Starter Guide for
Natty (Cactus), Oneiric (Diablo), Precise (Essex) soon to be completed
How: Updated through bzr/Launchpad merge processes.

Where:
http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin
What: 12.04 Quick Start from Hastexo. It's a great doc, but I think it
could receive even more attention and updates if it were in the OpenStack
docs umbrella, so I'm talking to the authors about submitting it.

Who:
Deployers of OpenStack clouds (public and private), proof-of-concept
creators

__API info__
Where:
http://github.com/openstack/openstack-manuals
http://github.com/openstack/object-api
http://github.com/openstack/compute-api
http://github.com/openstack/netconn-api
http://github.com/openstack/identity-api
http://github.com/openstack/image-api
What:
openstack-manuals contains:
- docs.openstack.org
  - API Quick Start
  - Compute API Programmer’s Guide
- api.openstack.org
  - OpenStack Compute extensions

Separate repos contain:
 (pointed to from docs.openstack.org/api)
- OpenStack Compute API Dev Guide
- OpenStack Object Storage API Dev Guide
- OpenStack Image API Dev Guide
- OpenStack Identity API Dev Guide
- OpenStack Quantum API Dev Guide

Note: In making this listing I realized that Melange has an API spec at
https://github.com/openstack/melange/blob/master/doc/source/apidoc.rst.
Their latest commit says they make it so it builds to rtfd.org but I can't
find it on that site. Note sent to Dan and Troy.

Who: API programmers, Python developers
How: Updated through the git/Gerrit review process.

__Wiki__
Where: http://wiki.openstack.org
What: Release notes, project status and process information, very little
how-to
Who: Contributors to the OpenStack projects

__Developer info__
Where: http://github.com/openstack/nova/
http://github.com/openstack/swift/
http://github.com/openstack/keystone/
http://github.com/openstack/glance/
http://github.com/openstack/horizon/
http://github.com/openstack/openstack-ci/

What:
http://nova.openstack.org
http://swift.openstack.org
http://keystone.openstack.org
http://glance.openstack.org
http://horizon.openstack.org
http://ci.openstack.org

__Main website__
Where: Silverstripe CMS with a few people with logins
What: openstack.org and all pages in it
Who: People who want to learn about OpenStack, community members, company
members

__Related websites__
Where: http://github.com/openstack-dev/devstack
What: http://devstack.org

Where: not sure, probably Silverstripe CMS with a few people with logins
What: http://trystack.org
Who: People who want to learn about OpenStack, community members, company
members

__Third party blogs and websites__
Where: The Internet
What: How-to and conceptual information about OpenStack
Who: Bloggers
How: I tend to link to good how-to information from bloggers at
http://wiki.openstack.org/BloggersTips. Better curation methods would be
great. I also contact bloggers directly and work with them to bring in CC
licensed content to openstack-manuals.

Yes, this is a long list. Yes, this is the Internet. Yes, I have ideas for
how to manage all this content, and I'd welcome yours as well.

Thanks for reading this far! Join us at the Summit to discuss in person.
Anne
___
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] [Doc] Docs meeting today, Monday 2000 UTC (3:00 CST)

[Anne Gentle]

Hi all,
If you're interested in the state of the docs and planning docs sessions
for the Design Summit, please attend this afternoon's doc team meeting.
Feel free to add to the agenda at wiki.openstack.org/Meetings/DocTeamMeeting
.


   - Action items from the last meeting
   - Design Summit planning
   - General documentation status
   - api.openstack.org site and extensions
   - Open discussion

Thanks,
Anne
___
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] [Doc] Docs meeting today, Monday 2000 UTC (3:00 CST)

[Anne Gentle]

It used to be 2:00 CST but now it's 3:00 CST.

Here's the UTC converter I used:

http://timeanddate.com/worldclock/meetingtime.html?iso=20120409&p1=400

Thanks for checking! Please confirm my methods are correct. :)

Anne

On Mon, Apr 9, 2012 at 10:13 AM, Lorin Hochstein
wrote:

> Anne:
>
> Can you confirm the time? The wiki page says March 9, 2012, 2000 UTC (3:00
> CST).
>
>  But isn't 2000 UTC the same as 1:00 PM CDT?
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
>
>
>
>
> On Apr 9, 2012, at 10:57 AM, Anne Gentle wrote:
>
> Hi all,
> If you're interested in the state of the docs and planning docs sessions
> for the Design Summit, please attend this afternoon's doc team meeting.
> Feel free to add to the agenda at
> wiki.openstack.org/Meetings/DocTeamMeeting.
>
>
>- Action items from the last meeting
>- Design Summit planning
>- General documentation status
>- api.openstack.org site and extensions
>- Open discussion
>
> Thanks,
> Anne
> ___
> 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] Endpoints problems

[Anne Gentle]

Hi Guilherme -
Sorry you ran into a doc bug -
https://bugs.launchpad.net/openstack-manuals/+bug/977905.

Basically, the bug states that the nova endpoint definition should be:

keystone --token 012345SECRET99TOKEN012345 --endpoint
http://192.168.206.130:35357/v2.0 endpoint-create \

   --region RegionOne \
   --service_id=abc0f03c02904c24abdcc3b7910e2eed \
   --publicurl
http://192.168.206.130:8774/v2/$(tenant_id)s \
   --adminurl
http://192.168.206.130:8774/v2/$(tenant_id)s \
   --internalurl
http://192.168.206.130:8774/v2/$(tenant_id)s

I haven't fixed this yet because I'm not sure if the $(tenant_id)s is
literal or which tenant_id specifically to use (the Service tenant for the
adminurl possibly)?

If someone on the list could offer more input here and on the doc bug it
would be greatly appreciated!
Anne

On Thu, Apr 12, 2012 at 12:25 PM, Guilherme Birk wrote:

>  I'm having problems setting up the nova endpoint. I've followed the
> manual
> http://docs.openstack.org/trunk/openstack-compute/install/content/setting-up-tenants-users-and-roles.html,
> putting the tenant id on the url's, like the manual says to do. But when I
> try execute "nova list" I got a malformed url error. When I set the
> endpoint without the tenant id on the url's I got a 404 error. Anyone
> having the same problem?
>
> I can access the dashboard normally, but I'm unable to retrieve instance
> list.
>
> ___
> 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] Endpoints problems

[Anne Gentle]

Thanks all!

And thanks for not saying "It's a Python Thing You Wouldn't Understand." :)

Yeah I do want a definitive answer but it's always good for me to learn to
read code.

Then again, things like replace('$(', '%(') make me go hmm...

One last clarification, this $(tenant_id)s should be used for both nova and
volume endpoints, right?

Thanks,

Anne


On Thu, Apr 12, 2012 at 5:44 PM, Pete Zaitcev  wrote:

> On Thu, 12 Apr 2012 15:28:21 -0500
> Anne Gentle  wrote:
>
> > keystone --token 012345SECRET99TOKEN012345 --endpoint
> > http://192.168.206.130:35357/v2.0 endpoint-create \
> >[]
> >--internalurl
> > http://192.168.206.130:8774/v2/$(tenant_id)s
> >
> > I haven't fixed this yet because I'm not sure if the $(tenant_id)s is
> > literal or which tenant_id specifically to use (the Service tenant for
> the
> > adminurl possibly)?
>
> The expression "$(tenant_id)s" is really contained inside the pattern
> in the database. It is substituded with a specific tennant ID when
> an application makes its request. The weird syntax is inherited from
> Python, where one can use constructs like %s or %(key)s.
>
> -- Pete
>
___
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] New Gerrit version (and server)

[Anne Gentle]

Thanks James and team for the work here, this will be very useful for
documentation drafts.

Anne

On Fri, Apr 13, 2012 at 8:55 AM, Sandy Walsh wrote:

> Sounds awesome! Looking forward to Draft Changes, much needed.
>
> -S
>
>
> 
> From: 
> openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net[openstack-bounces+sandy.walsh=
> rackspace@lists.launchpad.net] on behalf of James E. Blair [
> cor...@inaugust.com]
> Sent: Thursday, April 12, 2012 8:23 PM
> To: OpenStack Mailing List
> Subject: [Openstack] New Gerrit version (and server)
>
> Hi,
>
> We've just upgraded Gerrit to version 2.3.  There are a lot of changes
> behind the scenes that we've been looking forward to (like being able to
> store data in innodb rather than myisam tables for extra data
> longevity).  And there are a few visible changes that may be of interest
> to OpenStack developers.
>
> One new addition in 2.3 is "draft changes".  The idea behind a draft
> change in Gerrit is that it is a change that is not ready for merging,
> or even general code review, but you would like to share it with some
> people to get early comments.  If you upload a change as a draft, by
> default, no one else can see it.  You must explicitly add each person
> you would like to share it with as a reviewer.  Reviewers you add can
> leave comments, but can not vote at this stage.  You can continue to
> upload new patchsets to the change as it evolves, and once it is ready
> for general review, you can click the "Publish" button.  It will then
> become a normal change in Gerrit that everyone can see, including the
> earlier reviews from the draft stage.  This is a one way transition;
> once a draft is published, it can't be made a draft again.
>
> If you're using git-review from source or the latest version from PyPI
> (version 1.16, released today), you can easily upload a draft change by
> adding the "-D" option (eg, "git review -D").  Earlier versions of
> git-review also have the "-D" option, but the git ref that Gerrit uses
> to indicate a change should be a draft was changed between the 2.3
> release candidate and the final release; so if using "-D" results in an
> error, you may need to upgrade.
>
> You may notice some changes to the diff view.  Notably, the header which
> contained all of the possible viewing options has been split up into
> several parts; you can switch between them by selecting options that
> show up under the menu at the top.  I recommend setting "Retain Header
> On File Switch" under the Preferences section, as it is a nicer
> experience when changing files.
>
> Another notable new feature is the ability to add a group to the list of
> reviewers for a change.  Just type in the name of the group and click
> "Add Reviewer" and all of the individuals in the group will be added to
> the list of reviewers (and will see the change on their "review
> requests" list.
>
> Finally, we've modified some of our local OpenStack style changes so
> that it is easier for us to track upstream changes in layout.  It should
> mean a little more consistency throughout the interface, though we
> weren't able to keep the alternating row colors on the main table
> without a disproportionate amount of effort.  Do note that you can click
> on a line in a table, and it will be highlighted to improve legibility.
>
> We've tried to give this as much testing as possible before moving it
> into production.  If you encounter any issues, please let us know on IRC
> (mtaylor, jeblair, LinuxJedi), via email at
> , or you can file a bug at:
>
>  https://bugs.launchpad.net/openstack-ci/
>
> Thanks,
>
> Jim
>
> ___
> 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] Just JSON, and extensibility

[Anne Gentle]

Hi Mark,


> However, I question whether it's even being used in this fashion. Looking
> at our docs for Nova <
> http://docs.openstack.org/api/openstack-compute/2/content/>, the schema
> isn't locatable, and the XML Namespace <
> http://docs.openstack.org/compute/api/v1.1> is a 404. How are they
> finding the schema, and how is it getting into these tools?
>
>
>
The schema is available at
http://docs.openstack.org/api/openstack-compute/2/xsd/

I am told that we don't need to redirect to the XML Namespace as it is just
a string not an actual URL. If you disagree, please log a doc bug at
http://bugs.launchpad.net/openstack-manuals/ and tag it with compute-api
with specifics about how you think it should work on the docs site.


I'm not talking about *removing* XML from the current APIs that ship it,
> BTW; at most I'd like to see us:
>
> 1. Not require XML for new APIs, and
> 2. Talk about deprecating XML support in current ones (i.e., still support
> it, but de-emphasise it in documentation, don't expend new effort on it),
> and
> 3. Put some considered caveats around our current use of WADL and XML
> Schema.
>
>
One additional comment about WADL - basically one of those caveats. We had
little community traction documenting Compute API extensions with various
templates. A working solution now is to add extensions to
api.openstack.orgusing WADL and JSON samples. It's one of those
examples of elbow grease and
a small group adding great value. Next week I'll be doing a "Show-N-Tell"
of the api.openstack.org site first thing Monday morning as well as on a
panel about TryStack Thursday afternoon and would love feedback.

Thanks,
Anne




> Cheers,
>
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>
>
>
>
> ___
> 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 in centos 6.2 install document

[Anne Gentle]

Hi Shake -

We have been updating the install guide more often than the admin manual as
doc bugs are reported. Please review the latest revision at:

https://review.openstack.org/#/c/6615/

You can contribute to it through
http://github.com/openstack/openstack-manuals or by doing reviews. Also,
please log doc bugs as you see them. These are the latest being fixed with
the above review request:

bug 983417 , bug
984106

If you have specific doc bugs for the Compute Admin manual, please report
them (and fix them) through http://bugs.launchpad.net/openstack-manuals.

Thanks,
Anne

On Tue, Apr 17, 2012 at 6:18 PM, Shake Chen  wrote:

> Essex publish, lack of the English document.
>
> the document
> http://docs.openstack.org/trunk/openstack-compute/admin/content/
>
> not update.
>
> How to improve it?
>
>
>
>
>
>
> 2012/4/18 Jan Drake 
>
>> any chance of an english version?
>>
>>
>>
>> On Apr 16, 2012, at 9:03 AM, darkfower  wrote:
>>
>> > hi,every one:
>> >
>> > The attachment is I wrote in the installation of openstack centos 6.2
>> document
>> > 
>> > ___
>> > 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
>>
>
>
>
> --
> 陈沙克
> 手机：13661187180
> msn：shake.c...@hotmail.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
>
>
___
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] "Shutoff" Status

[Anne Gentle]

Hi all -
We just added descriptions of each of the statuses to this page, but
"SUSPENDED" is not one of them:

http://docs.openstack.org/api/openstack-compute/2/content/List_Servers-d1e2078.html

Who has more information about this server status? By grepping the code I
get this additional info which may mean it only applies to bare metal
deploy and/or xenapi?

./nova/api/ec2/cloud.py:vm_states.SUSPENDED: inst_state.SUSPEND,
./nova/api/openstack/common.py:vm_states.SUSPENDED: {
./nova/api/openstack/common.py:'default': 'SUSPENDED',
./nova/compute/api.py:
@check_instance_state(vm_state=[vm_states.SUSPENDED])
./nova/compute/api.py:vm_state=vm_states.SUSPENDED,
./nova/compute/manager.py:
vm_state=vm_states.SUSPENDED,
./nova/compute/power_state.py:SUSPENDED = 0x07
./nova/compute/power_state.py:SUSPENDED: 'suspended',
./nova/compute/vm_states.py:SUSPENDED = 'suspended'
./nova/tests/baremetal/test_proxy_bare_metal.py:
dict(node_id=8, name='i-0008', status=power_state.SUSPENDED),
./nova/tests/test_compute.py:   {'vm_state':
vm_states.SUSPENDED})
./nova/tests/test_compute.py:search_opts={'power_state':
power_state.SUSPENDED})
./nova/virt/baremetal/proxy.py:'power_state':
power_state.SUSPENDED})
./nova/virt/xenapi/vm_utils.py:'Suspended': power_state.SUSPENDED,

Thanks,
Anne

On Mon, Apr 23, 2012 at 9:24 AM, Razique Mahroua
wrote:

> Hello Alyssa, the status is the one reported when you suspend your instance
>
> *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 16 avr. 2012 à 18:15, Alyssa Hurtgen a écrit :
>
>  Hi all,
>
>  I work at Rackspace and noticed a new Nova server status of "shutoff".
>
>- What does this status mean?
>- How does the server get into this status?
>- Should the user be able to perform any actions against the server?
>
> Thanks,
> Alyssa Hurtgen
>  ___
> 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] "Shutoff" Status

[Anne Gentle]

Hey, sorry y'all. I grepped for SUSPENDED but needed to do it for SHUTOFF.
What can you tell me about SHUTOFF based on the code here?

Yep, not too embarrassed to admit this to 3000+ of you. :)

./nova/api/ec2/cloud.py:vm_states.SHUTOFF: inst_state.SHUTOFF,
./nova/api/ec2/cloud.py:if (vm_state == vm_states.SHUTOFF and
./nova/api/ec2/cloud.py:if vm_state not in (vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/api/ec2/cloud.py:if vm_state in (vm_states.ACTIVE,
vm_states.SHUTOFF):
Binary file ./nova/api/ec2/cloud.pyc matches
./nova/api/ec2/inst_state.py:SHUTOFF = 'shutoff'
./nova/api/ec2/inst_state.py:SHUTOFF: TERMINATED_CODE,
Binary file ./nova/api/ec2/inst_state.pyc matches
./nova/api/openstack/common.py:vm_states.SHUTOFF: {
./nova/api/openstack/common.py:'default': 'SHUTOFF',
Binary file ./nova/api/openstack/common.pyc matches
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/compute/api.py:
vm_states.SHUTOFF, vm_states.STOPPED])
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/compute/api.py:
@check_instance_state(vm_state=[vm_states.STOPPED, vm_states.SHUTOFF])
./nova/compute/api.py:if vm_state == vm_states.SHUTOFF:
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF])
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF])
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF],
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF],
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF],
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF],
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
./nova/compute/api.py:@check_instance_state(vm_state=[vm_states.ACTIVE,
vm_states.SHUTOFF,
Binary file ./nova/compute/api.pyc matches
./nova/compute/manager.py:
power_state.SHUTOFF,
./nova/compute/manager.py:
vm_state=vm_states.SHUTOFF)
Binary file ./nova/compute/manager.pyc matches
./nova/compute/power_state.py:SHUTOFF = 0x05
./nova/compute/power_state.py:SHUTOFF: 'shutdown',
Binary file ./nova/compute/power_state.pyc matches
./nova/compute/vm_states.py:SHUTOFF = 'shutoff'
Binary file ./nova/compute/vm_states.pyc matches
./nova/tests/api/ec2/test_cloud.py:
test_instance_state(inst_state.TERMINATED_CODE, inst_state.SHUTOFF,
./nova/tests/api/ec2/test_cloud.py:
power_state.NOSTATE, vm_states.SHUTOFF)
./nova/tests/api/ec2/test_cloud.py:
power_state.NOSTATE, vm_states.SHUTOFF,
./nova/tests/baremetal/test_proxy_bare_metal.py:
dict(node_id=6, name='i-0006', status=power_state.SHUTOFF),
./nova/tests/fakelibvirt.py:VIR_DOMAIN_SHUTOFF = 5
./nova/tests/fakelibvirt.py:self._state = running and
VIR_DOMAIN_RUNNING or VIR_DOMAIN_SHUTOFF
./nova/tests/fakelibvirt.py:self._state = VIR_DOMAIN_SHUTOFF
./nova/tests/test_compute.py:'vm_state':
vm_states.SHUTOFF})
./nova/tests/test_compute.py:check_state(instance_uuid,
power_state.NOSTATE, vm_states.SHUTOFF,
./nova/tests/test_compute.py:  power_state.NOSTATE,
vm_states.SHUTOFF, None)
./nova/tests/test_libvirt.py:return {'state':
power_state.SHUTOFF}
./nova/virt/libvirt/connection.py:if state ==
power_state.SHUTOFF:
./nova/virt/libvirt/connection.py:
power_state.SHUTOFF,
Binary file ./nova/virt/libvirt/connection.pyc matches


On Mon, Apr 23, 2012 at 10:02 PM, Anne Gentle  wrote:

> Hi all -
> We just added descriptions of each of the statuses to this page, but
> "SUSPENDED" is not one of them:
>
>
> http://docs.openstack.org/api/openstack-compute/2/content/List_Servers-d1e2078.html
>
> Who has more information about this server status? By grepping the code I
> get this additional info which may mean it only applies to bare metal
> deploy and/or xenapi?
>
> ./nova/api/ec2/cloud.py:vm_states.SUSPENDED: inst_state.SUSPEND,
> ./nova/api/openstack/common.py:vm_states.SUSPENDED: {
> ./nova/api/openstack/common.py:'default': 'SUSPENDED',
> ./nova/compute/api.py:
> @check_instance_state(vm_state=[vm_states.SUSPENDED])
> ./nova/compute/api.py:vm_state=vm_states.SUSPENDED,
> ./nova/compute/manager.py:
> vm_state=vm_states.SUSPENDED,
> ./nova/compute/power_state.py:SUSPENDED = 0x07
> ./nova/compute/power_state.py:SUSPENDED: 'suspended&

Re: [Openstack] Quantum Integration Part 3

[Anne Gentle]

Ah, the Jenkins job copies to "incubated" and it should be "incubation" -
fixing now.
Anne

On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt  wrote:

> Hi Alan,
>
> That's a good question.  I had assumed that my recent commits to
> https://www.github.com/openstack/openstack-manuals would
> automatically propagate to
> http://docs.openstack.org/incubation/openstack-network/admin/content/index.html,
>  but that doesn't seem to have happened for the latest commits.
>
> Anne Gentle, can you help out here?  Thanks!
>
> Dan
>
> On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh  > wrote:
>
>> **
>> Hi Dan
>>
>> When will the revised Quantum Admin Guide be posted?
>>
>> Alan
>>
>>  --
>> *From:* 
>> openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto:
>> openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On
>> Behalf Of *Dan Wendlandt
>> *Sent:* April-25-12 1:55 PM
>> *To:* Emilien Macchi
>> *Cc:* openstack@lists.launchpad.net
>> *Subject:* Re: [Openstack] Quantum Integration Part 3
>>
>>  Hi Emilien,
>>
>> On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi <
>> emilien.openst...@gmail.com> wrote:
>>>
>>>
>>> For example, Quantum does not work with Keystone : When nova-network
>>> send an API call to Quantum-server, the token is missing in the HTTP
>>> HEADER. I've disabled Keystone at this time.
>>>
>>
>> That is correct.  In the Quantum Admin Guide, it explains some work that
>> was done to support Keystone Authn, but notes that this is all
>> experimental, as the Quantum API does not support Authz.  This is because
>> the only person that calls Quantum in Essex is Nova itself.  Troy Toman's
>> team is working on Quantum Authz for Folsom, so the API can be exposed
>> directly to tenants.
>>
>>
>>>
>>>
>>> *- What is working at this time :*
>>>
>>> - Quantum-Server with MySQL
>>> - Quantum-Agent (with OVS) on each nova-compute node
>>> - OVS bridge with eth1
>>> -  nova-network seems working with Quantum
>>>
>>> *- What is not working (yet !) :*
>>>
>>> - When I create an instance (from dashboard or with Nova CLI), the
>>> network is created with Quantum, an private IP is attributed to the
>>> instance, but when I check the instance log file, the network interface
>>> doesn't get an IP adress. Here the log :
>>> http://paste.openstack.org/show/13821
>>>
>>
>> Are you able to access the VM via VNC?  If you statically configure the
>> IP does it work?  What happens if you run dhcpc manually?
>>
>> I would look in the nova-network logs and see if you see an errors
>> related to DHCP.
>>
>>
>>>
>>> - Horizon with Quantum : I can't integrate Quantum in the dashboard
>>> even with
>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
>>>
>>
>> Essex Horizon does not support Quantum.  Its actually not just a Horizon
>> thing, it has to do with how the Nova + Quantum integration works.  Each
>> Quantum network has to be associated with appropriate IPAM subnet, meaning
>> the existing .  For now, you need to create networks using nova-manage.  If
>> you want VMs to get the default set of NICs, you can then boot them with
>> Horizon.  If you want to specify what networks vNICs are plugged into, this
>> is only supported via the nova boot command with the --nic option.  I'll
>> flush this out in more detail in the Quantum Admin Guide.
>>
>> Dan
>>
>>
>>>
>>>
>>>
>> --
>> ~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com
>> twitter: danwendlandt
>> ~~~
>>
>>
>
>
> --
> ~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~
>
>
___
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 Integration Part 3

[Anne Gentle]

All fixed up, let me know if you have any other issues. Thanks Jim Blair
for the help.

Anne

On Fri, Apr 27, 2012 at 10:57 AM, Anne Gentle  wrote:

> Ah, the Jenkins job copies to "incubated" and it should be "incubation" -
> fixing now.
> Anne
>
>
> On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt  wrote:
>
>> Hi Alan,
>>
>> That's a good question.  I had assumed that my recent commits to
>> https://www.github.com/openstack/openstack-manuals would
>> automatically propagate to
>> http://docs.openstack.org/incubation/openstack-network/admin/content/index.html,
>>  but that doesn't seem to have happened for the latest commits.
>>
>> Anne Gentle, can you help out here?  Thanks!
>>
>> Dan
>>
>> On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh <
>> alan.kavan...@ericsson.com> wrote:
>>
>>> **
>>> Hi Dan
>>>
>>> When will the revised Quantum Admin Guide be posted?
>>>
>>> Alan
>>>
>>>  --
>>> *From:* 
>>> openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto:
>>> openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On
>>> Behalf Of *Dan Wendlandt
>>> *Sent:* April-25-12 1:55 PM
>>> *To:* Emilien Macchi
>>> *Cc:* openstack@lists.launchpad.net
>>> *Subject:* Re: [Openstack] Quantum Integration Part 3
>>>
>>>  Hi Emilien,
>>>
>>> On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi <
>>> emilien.openst...@gmail.com> wrote:
>>>>
>>>>
>>>> For example, Quantum does not work with Keystone : When nova-network
>>>> send an API call to Quantum-server, the token is missing in the HTTP
>>>> HEADER. I've disabled Keystone at this time.
>>>>
>>>
>>> That is correct.  In the Quantum Admin Guide, it explains some work that
>>> was done to support Keystone Authn, but notes that this is all
>>> experimental, as the Quantum API does not support Authz.  This is because
>>> the only person that calls Quantum in Essex is Nova itself.  Troy Toman's
>>> team is working on Quantum Authz for Folsom, so the API can be exposed
>>> directly to tenants.
>>>
>>>
>>>>
>>>>
>>>> *- What is working at this time :*
>>>>
>>>> - Quantum-Server with MySQL
>>>> - Quantum-Agent (with OVS) on each nova-compute node
>>>> - OVS bridge with eth1
>>>> -  nova-network seems working with Quantum
>>>>
>>>> *- What is not working (yet !) :*
>>>>
>>>> - When I create an instance (from dashboard or with Nova CLI), the
>>>> network is created with Quantum, an private IP is attributed to the
>>>> instance, but when I check the instance log file, the network interface
>>>> doesn't get an IP adress. Here the log :
>>>> http://paste.openstack.org/show/13821
>>>>
>>>
>>> Are you able to access the VM via VNC?  If you statically configure the
>>> IP does it work?  What happens if you run dhcpc manually?
>>>
>>> I would look in the nova-network logs and see if you see an errors
>>> related to DHCP.
>>>
>>>
>>>>
>>>> - Horizon with Quantum : I can't integrate Quantum in the dashboard
>>>> even with
>>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
>>>>
>>>
>>> Essex Horizon does not support Quantum.  Its actually not just a Horizon
>>> thing, it has to do with how the Nova + Quantum integration works.  Each
>>> Quantum network has to be associated with appropriate IPAM subnet, meaning
>>> the existing .  For now, you need to create networks using nova-manage.  If
>>> you want VMs to get the default set of NICs, you can then boot them with
>>> Horizon.  If you want to specify what networks vNICs are plugged into, this
>>> is only supported via the nova boot command with the --nic option.  I'll
>>> flush this out in more detail in the Quantum Admin Guide.
>>>
>>> Dan
>>>
>>>
>>>>
>>>>
>>>>
>>> --
>>> ~~~
>>> Dan Wendlandt
>>> Nicira, Inc: www.nicira.com
>>> twitter: danwendlandt
>>> ~~~
>>>
>>>
>>
>>
>> --
>> ~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com
>> twitter: danwendlandt
>> ~~~
>>
>>
>
___
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] Proposal for manuals translation process

[Anne Gentle]

Hi Daisy,

Thanks so much for this detailed proposal. I'd like you to put it on the
OpenStack wiki, at http://wiki.openstack.org/Translations.

My first read-through and discussion with the CI team brings up a few
comments:
- Whatever we do for docs, we should also do for code strings. So
unfortunately the scope for the "Goal" probably cannot be so narrow. We
know Launchpad to be broken with code strings now, that data point should
be reflected in this point-in-time analysis.

- Dashboard uses Transifex now (while the other projects unsuccessfully use
Launchpad). Tres Henry, can you comment on the number of translators of
Dashboard strings you have on the Transifex side already?

- Not that I want analysis paralysis, but, we may need to add a third
column of a crowd-sourced translation option like Pootle that is familiar
to open-source translators. Also, the lack of a translation
memory/dictionary (and having to hold such a valuable asset in a wiki page)
is troubling, can we also analyze an option that offers a translation
dictionary? So much re-use would be available to all the projects.

- There seems to be assumptions that Jenkins and Gerrit will "just work"
with out much description of the role those two crucial tools play. Can you
further describe the workflow for those in the Slicing, Uploading,
Downloading, Converging, and Generating steps?

I appreciate all the hard work I _know_ went into this proposal. Let's get
it on the wiki, discuss more, and keep adding details. I'd like to make
this a blueprint, could be for openstack-manuals, could be for horizon, I
don't know yet. Thanks for stepping up and embracing our international
community's needs!

Thanks,
Anne





On Fri, Apr 27, 2012 at 3:45 AM, Ying Chun Guo  wrote:

> Hi, all
>
> During the "I18N in OpenStack" discussion in design summit, it is
> mentioned that documents need to I18N. I also noticed some requests for a
> Chinese version manuals from China users. But unlike Gettext strings in the
> codes,  there is no process for DocBook translation yet. Translators, who
> want to help translation, have to take a DocBook into a tool and perform
> a translation on a copy which will be saved as a new file. This
> traditional translation model is not good for collaboration. Usually, the
> open source translation depends on volunteers. It's better to use the crowd
> translation model, which enables a mass of translators to work on the
> same job, just like the Launchpad Web UI for Gettext strings translation,
> any people can jump in at any time and contribute to any part of the
> translatable contents.
>
> In order to facilitate the manuals translation, I investigated several
> translation websites and several open source projects. I composed this
> proposal. Now it's open for suggestions and comments.
>
> *Goal*
> **
> A process for manuals translation
>
> *Background*
> *--*
> OpenStack Manuals are in DocBook format. The source is on GitHub:
> http://github.com/openstack/openstack-manuals
> Launchpad and Transifex are free web based tools used for crowd
> translation. Both of them provide a simple web interface in which
> non-technical people can help translation. They don't support DocBook
> format, but support the popular GNU Gettext file formats (PO Template or
> PO).
>
> *Translation Process*
> *---*
> In order to translate OpenStack Manuals to multiple languages, which are
> in DocBook format, we can slice the documents into short statements, then
> use a web based translation management tool to manage the translation
> process, and finally converge the translated content into a new copy of
> DocBook.
>
> Here are the five steps of the translation process:
> Step #1 Slicing - extract translatable content from DocBooks and generate
> Gettext compatible POT files (PO Template or PO);
> Step #2 Uploading - upload the POT (or PO) files to a web based
> translation management tool;
> Step #3 Downloading - download PO (or MO) files from the web tool after
> translation and review;
> Step #4 Converging - converge the translated contents into new copies of
> DocBook, create DocBooks in multiple languages
> Step #5 Generating - generate HTML/PDF in multiple languages from DocBooks
> in multiple languages
>
> The picture in the attachment describes these steps.
> *(See attached file: DocBook translation process.png)*
>
> *Compare of Launchpad and Transifex*
> *---*
> Launchpad (https://launchpad.net/) and Transifex (
> https://www.transifex.net/) are similar web based tools used for crowd
> translation. The goal of the compare is to find the most appropriate tool
> for this scenario. The compare are made between Launchpad and Transifex
> free version for open sources. (Refer to https://www.transifex.net/plans/ to
> get details of “Transifex free version for open sources”)
>
> After considering the requirements for manuals translation,  below
> perspectives are taking into consideration:
> *Support

[Openstack] Documentation internship in Austin, TX at Rackspace

[Anne Gentle]

Hi all -
We're hiring a summer intern at Rackspace to help with OpenStack
documentation. Please forward to all college (or graduate) students who
will be in the Austin area this summer so they can apply through this link:

http://jobs.rackspace.com/job/Austin-Intern-I-US-Job-TX-73301/1861960/

Here's a more detailed job description.

Create and deliver materials in collaboration with developers, writers, and
community members. Materials cover implementations of cloud computing using
the open source OpenStack projects including OpenStack Compute and
OpenStack Object Storage as well as an Image Service and Identity Service
with a web-based Dashboard. These projects are collaboratively developed
with partners in the OpenStack community.



Ideally the candidate can:



* Edit existing or develop new technical content including:

  - Administration manuals (installation and configuration, large
scale deployment)

  - API developer manuals (REST-based APIs)

  - Python developer documentation

* Work on a backlog of documentation bugs as well as triage incoming
bugs

* Work with engineering, QA, and support organizations to the benefit
of OpenStack

* Work with OpenStack community members to implement technical
solutions to documentation issues


Please apply through the link above and feel free to contact me with any
questions you have.


Thanks,

Anne



Anne Gentle | http://justwriteclick.com/

[image: Facebook] <http://facebook.com/conversationandcommunity>[image:
Linkedin] <http://linkedin.com/annegentle>[image:
Twitter]<http://twitter.com/annegentle>
___
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 Essex - Guide for Ubuntu 12.04

[Anne Gentle]

Hi Emilien -
Ideally Martin's guide and your guide would be part of the OpenStack
documentation - your licensing would work within our framework for docs.

Martin, how is progress going on submitting your Quick Start guide through
the Gerrit review process?

Thanks,
Anne


Anne Gentle | http://justwriteclick.com/

[image: Facebook] <http://facebook.com/conversationandcommunity>[image:
Linkedin] <http://linkedin.com/annegentle>[image:
Twitter]<http://twitter.com/annegentle>


On Mon, Apr 30, 2012 at 6:46 AM, Loic Dachary  wrote:

> On 04/30/2012 10:52 AM, Martin Gerhard Loschwitz wrote:
> > Am 30.04.12 09:41, schrieb Emilien Macchi:
> >> Hi,
> >>
> >> I release my first documentation on OpenStack Essex for Ubuntu 12.04.
> >>
> >> I've been working for three weeks with StackOps for my internship, and
> my work is focused ont Quantum (Networking as a service in OpenStack).
> >>
> >>
> >> It was quite difficult to have a working infrastructure because Quantum
> is only in "incubation" for Essex release. That's why I publish a
> documentation in which anyone can test this fabulous software.
> >>
> >> You can find this documentation in attachment and here <
> https://github.com/EmilienM/doc-openstack> with all configuration files &
> scripts.
> >>
> >>
> >> *Please let me know if I did some mistakes, and of course I will do by
> best tocorrect it.*
> >>
> >>
> >> Best regards
> >>
> > Hello there,
> >
> > that's fabolous work, thanks a lot! I'd be interested in integrating
> parts of
> > this into the hastexo OpenStack installation guide if you don't mind --
> what
> > license is your documentation published under, and would you agree to
> such a
> > step? :)
> >
> > Best regards
> > Martin G. Loschwitz
> >
> Hi,
>
> stackops chose to release under Creative Commons – Attribution-ShareAlike
> 3.0 ( https://github.com/EmilienM/doc-openstack/blob/master/README ),
> which allows all redistribution as long as you keep the credits and the
> copyleft license.
>
> Emilien, in order for people to improve your document you should add the
> sources of the document to https://github.com/EmilienM/doc-openstack .
> Otherwise it needs to be copied over and you'll have a hard time
> incorporating pull requests.
>
> Good work :-)
>
> --
> Loïc Dachary Chief Research Officer
> // eNovance labs   http://labs.enovance.com
> // ✉ l...@enovance.com  ☎ +33 1 49 70 99 82
>
>
> ___
> 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 Essex - Guide for Ubuntu 12.04

[Anne Gentle]

Hi Daniel - 
Thanks for thinking of that document as well. 

The goal is to bring documents specific to OpenStack into a doc system with bug 
tracking, testing, editing, and community contributor access. Eventually 
translation may be available.  

I'd like to avoid the fragmentation and doubt I hear about the docs by applying 
systems discipline to as many relevant docs as possible.

The process for contributing docs is described here: 
Http://wiki.openstack.org/Documentation/HowTo

Thanks,
Anne

Anne Gentle
Content Stacker
a...@openstack.org


On Apr 30, 2012, at 7:40 AM, "Daniel P. Berrange"  wrote:

> On Mon, Apr 30, 2012 at 07:26:17AM -0500, Anne Gentle wrote:
>> Hi Emilien -
>> Ideally Martin's guide and your guide would be part of the OpenStack
>> documentation - your licensing would work within our framework for docs.
>> 
>> Martin, how is progress going on submitting your Quick Start guide through
>> the Gerrit review process?
> 
> Your suggestion implies that OpenStack upstream is OK with having downstream
> distro-specific setup docs. If that's the case we have an equivalent getting
> started guide for Essex on Fedora 17:
> 
>  https://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17
> 
> This wiki content is under "Creative Commons Attribution-Share Alike License
> 3.0 Unported" [1]
> 
> Regards,
> Daniel
> 
> [1] https://fedoraproject.org/wiki/Legal/Licenses#This_Website
> -- 
> |: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org  -o- http://virt-manager.org :|
> |: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
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] URL Scheme for deploying Openstack in HTTPD

[Anne Gentle]

My vote is for service/API names. This convention is what the documentation
uses whenever possible.
http://wiki.openstack.org/Documentation/Conventions

Thanks,
Anne

On Mon, Apr 30, 2012 at 2:30 PM, Adam Young  wrote:

>  On 04/30/2012 02:58 PM, Dolph Mathews wrote:
>
> I very much like the idea that we should have a well documented
> recommendation on this topic.
>
>  My only criticism is that the API/service names should be used in place
> of project names, e.g. https://hostname/identity, https://hostname/compute,
> etc.
>
>
> I think we can propose both,  and let people weigh in.  I'm of equal mind,
> to be honest,  and could see and argument for Keystone versus Identity.
>
> I'll treat it as one vote for each thus far.  THe Vote for the project
> name came from  bere...@b1-systems.de
>
>
>
>
>  -Dolph
>
> On Mon, Apr 30, 2012 at 11:34 AM, Adam Young  wrote:
>
>  A production configuration of Openstack should be able to run in HTTPD
> using SSL.  I'd like to propose the following URL scheme for the web Apps
> so that the various pieces can be installed on a single machine without
> conflict.
>
> All pieces will be served on port 443 using the https protocol.
>
>
> I've written these up to use the project names.  Enough documentation and
> information around the projects has circulated such that replacing, say,
> Keystone with identity would cause more confusion than it would remove.
>
>
> #Web UI
> #If and only if this is installed,  we should put in a forward from / to
> /dashboard for browser clients.
> https://hostname/dashboard
>
>
> #identity
> https://hostname/keystone/main
> https://hostname/keystone/admin
>
> #image
> https://hostname/glance/api
> https://hostname/glance/registry
>
> #compute.  Not sure if all of these are required
> https://hostname/nova/api
> https://hostname/nova/crt
> https://hostname/nova/object
> https://hostname/nova/cpu
> https://hostname/nova/network
> https://hostname/nova/volume
> https://hostname/nova/schedule
> https://hostname/nova/novnc
> https://hostname/nova/vncx
> https://hostname/nova/cauth
>
> #network
> https://hostname/quantum/api 
> #if we had an API for the agent it would be
> https://hostname/quantum/agent 
>
>
> There was an attempt to make Swift also fit into this scheme.  However,
> Swift URLs fall into a scheme of their own,  and won't likely be colocated
> with the admin pieces outside of development.  Here they are for
> completeness.
>
> #storage
> https://hostname/swift/account
> https://hostname/swift/object
> https://hostname/swift/container
>
>
> The pattern here should be clear enough to extend to integrating projects
> not listed above.
>
>
>
> ___
> 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] Documentation: pdf link missing

[Anne Gentle]

Thanks Paras, this is a doc bug that keeps resurrecting itself. Opening
https://bugs.launchpad.net/openstack-manuals/+bug/992652

Today I'm cutting an Essex release for the docs so I'll be sure to address
this, thanks.

Anne

On Tue, May 1, 2012 at 9:51 AM, Paras pradhan wrote:

> The pdf icon in this link is not working.
>
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/
>
>
> Paras.
>
> ___
> 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] Documentation: pdf link missing

[Anne Gentle]

We have a somewhat working epub output, but CHM is not on the list in the
future. It's deprecated by Microsoft. Is there an offline, compressed HTML
need that you have? Let me hear more about your need.

Here's the info about epub:
http://www.openstack.org/blog/2011/11/hacking-on-ebooks/

We'll be hacking on epub and mobi again at Rackspace in May - all are
welcome to work on the Cloud docs plugin at
https://github.com/rackspace/clouddocs-maven-plugin to improve the output.

Thanks,
Anne

On Tue, May 1, 2012 at 10:25 AM, Paras pradhan wrote:

> Great Thanks. BTW are there another formats available? Like chm.
>
> Paras.
>
>
> On Tue, May 1, 2012 at 10:08 AM, Anne Gentle  wrote:
> > Thanks Paras, this is a doc bug that keeps resurrecting itself. Opening
> > https://bugs.launchpad.net/openstack-manuals/+bug/992652
> >
> > Today I'm cutting an Essex release for the docs so I'll be sure to
> address
> > this, thanks.
> >
> > Anne
> >
> > On Tue, May 1, 2012 at 9:51 AM, Paras pradhan 
> > wrote:
> >>
> >> The pdf icon in this link is not working.
> >>
> >>
> >> http://docs.openstack.org/trunk/openstack-compute/admin/content/
> >>
> >>
> >> Paras.
> >>
> >> ___
> >> 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] [Doc] Documentation releases

[Anne Gentle]

Hi all -
I've written down the steps I've discovered while doing the Essex branch
for the docs:

http://wiki.openstack.org/Documentation/Release

Please review and let me know if you have questions.

Thanks to the CI team (James Blair rocks!) for the assistance in creating
parameters so that this process is even easier.

After today, we should have a stable/essex branch for the openstack-manuals
repository, and the docs.openstack.org home page will point to Essex
documentation plus trunk, and the /essex pages will have Disqus comments
opened. Also, the /bexar and /cactus areas will redirect to /trunk.

Thanks,

Anne
___
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] [Doc] Documentation releases

[Anne Gentle]

Also, I forgot to also mention that the Quantum guides will move from
/incubation to /trunk. I'll do a redirect on the server-side for these URLs:

http://docs.openstack.org/incubation/openstack-network/developer/quantum-api-1.0/content/

http://docs.openstack.org/incubation/openstack-network/admin/content/

Thanks,
Anne

-- Forwarded message --
From: Anne Gentle 
Date: Wed, May 2, 2012 at 10:16 AM
Subject: [Doc] Documentation releases
To: openstack@lists.launchpad.net


Hi all -
I've written down the steps I've discovered while doing the Essex branch
for the docs:

http://wiki.openstack.org/Documentation/Release

Please review and let me know if you have questions.

Thanks to the CI team (James Blair rocks!) for the assistance in creating
parameters so that this process is even easier.

After today, we should have a stable/essex branch for the openstack-manuals
repository, and the docs.openstack.org home page will point to Essex
documentation plus trunk, and the /essex pages will have Disqus comments
opened. Also, the /bexar and /cactus areas will redirect to /trunk.

Thanks,

Anne
___
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 graphical ressources

[Anne Gentle]

Hi all -

Yep, we've had that request before. Problem is, the icons are in an ai file
and we haven't had the bandwidth to put them in something open and post
them somewhere. Plus they need to be sliced out one-by-one from the .ai
file. Anyone have Illustrator experience who wants to take on this task?
They're CC licensed, we just need to get them into a better format and in
separate files.

Thanks,

Anne



On Fri, May 4, 2012 at 6:40 AM, Atul Jha  wrote:

> Hi,
> 
> From: 
> openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
> csscorp@lists.launchpad.net] on behalf of Razique Mahroua [
> razique.mahr...@gmail.com]
> Sent: Friday, May 04, 2012 4:20 PM
> To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
> Subject: [Openstack] Openstack graphical ressources
>
> Hello all,
> do you guys know who manage the graphical aspect of OPS : icons,
> resources, templates, etc...
>
> +1
>
>
> I'd love to have it more developed. It would be cool to provide users some
> resources : icons for their desktops, wallpapers, maybe skins, application
> icons,etc...
> I just wanted to have a sexy OPS wallpaper this morning, but  this ain't a
> cool one http://goo.gl/nlWKq
>
> Thanks,
> Razique
> Nuage & Co - Razique Mahroua
> razique.mahr...@gmail.com
>
> [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique]
>
> Even i would love to see a space on openstack.org with say (branding),
> which has icons, wallpapers, posters, T-Shirt designs.
> This will help in say am organizing an Openstack based i will go there and
> use the source to get stuff printed.
> I am making a presentation slide and i have all the icons already
> available, i can simply use them.
>
>
>
> Atul
> 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
>
>
___
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 graphical ressources

[Anne Gentle]

Awesome! Here's the file. I think we can just post the separate files as an
attachment to a wiki page, nothing fancy needed. :) I can also post to
openstack.org (I think).

Let me know if you have any difficulty with the file.

Anne

On Fri, May 4, 2012 at 9:12 AM, Razique Mahroua
wrote:

> Yup,
> I can totally do it, I used to do webdesign before being a lazy sysadmin.
> I still have all the resources here.
> How do you want me to work on that ? and where could we host the resources
> afterwards ?
> Razique
>
>  *Nuage & Co - Razique Mahroua** *
> razique.mahr...@gmail.com
>
>
> Le 4 mai 2012 à 15:52, Anne Gentle a écrit :
>
> Hi all -
>
> Yep, we've had that request before. Problem is, the icons are in an ai
> file and we haven't had the bandwidth to put them in something open and
> post them somewhere. Plus they need to be sliced out one-by-one from the
> .ai file. Anyone have Illustrator experience who wants to take on this
> task? They're CC licensed, we just need to get them into a better format
> and in separate files.
>
> Thanks,
>
> Anne
>
>
>
> On Fri, May 4, 2012 at 6:40 AM, Atul Jha  wrote:
>
>> Hi,
>> 
>> From: 
>> openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
>> csscorp@lists.launchpad.net] on behalf of Razique Mahroua [
>> razique.mahr...@gmail.com]
>> Sent: Friday, May 04, 2012 4:20 PM
>> To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
>> Subject: [Openstack] Openstack graphical ressources
>>
>> Hello all,
>> do you guys know who manage the graphical aspect of OPS : icons,
>> resources, templates, etc...
>>
>> +1
>>
>>
>> I'd love to have it more developed. It would be cool to provide users
>> some resources : icons for their desktops, wallpapers, maybe skins,
>> application icons,etc...
>> I just wanted to have a sexy OPS wallpaper this morning, but  this ain't
>> a cool one http://goo.gl/nlWKq
>>
>> Thanks,
>> Razique
>> Nuage & Co - Razique Mahroua
>> razique.mahr...@gmail.com<mailto:razique.mahr...@gmail.com>
>>
>> [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique]
>>
>> Even i would love to see a space on openstack.org with say (branding),
>> which has icons, wallpapers, posters, T-Shirt designs.
>> This will help in say am organizing an Openstack based i will go there
>> and use the source to get stuff printed.
>> I am making a presentation slide and i have all the icons already
>> available, i can simply use them.
>>
>>
>>
>> Atul
>> 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
>>
>>
>
>
___
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] [Doc] Folsom blueprints for openstack-manuals

[Anne Gentle]

Hi all -
I'm working on blueprints for openstack-manuals for the Folsom release.
Here's what I'm going to register:

   1. Operations manual - outline at
   http://etherpad.openstack.org/EssexOperationsGuide
   2. Template for detailed configuration info for known deployments such
   as TryStack and Mediawiki, others who are interested like MercadoLibre (if
   you're interested, let me know)
   3. Enable quicker edits - this is related to a CI team blueprint,
   https://blueprints.launchpad.net/openstack-ci/+spec/ci-doc-automation
   4. Try-it-out on http://api.openstack.org
   5. Content sharing for API guides (
   
https://blueprints.launchpad.net/openstack-manuals/+spec/design-content-sharing
   )

If you have other blueprints you'd like to get in to the Folsom release,
let me know, or register them at
http://blueprints.launchpad.net/openstack-manuals.

I'll get more details into these next week, but wanted to get the ball
rolling for thoughts on the top doc goals for this release. We'll also
discuss at the next Doc Team meeting May 14th.

Thanks,
Anne
___
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] Install Your Own OpenStack Cloud - Essex Edition

[Anne Gentle]

Hi Eric -
Thanks for this documentation effort! I see you have licensed this document
under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Would
you be interested in contributing parts of the document to the OpenStack
documentation?

Here are the parts for which I see a fit:
Configure the Networking (nova-network) page 16-20
USE YOUR CLOUD page 25-48
Appendix A: page 48-49 (add to the glossary)

To contribute to the documentation, review
http://wiki.openstack.org/Documentation/HowTo#First-time_Contributors to
get started. Docs use the same process as development. The docs are stored
in a repository at http://github.com/openstack/openstack-manuals.

Feel free to follow up off-list with any questions you have.

Thanks,
Anne



On Mon, May 7, 2012 at 7:23 AM, Eric Dodemont wrote:

> I have written a 50 pages document: "Install Your Own OpenStack Cloud -
> Essex Edition".
>
> The PDF file can be downloaded here: http://tiny.cc/qstxdw
>
> In the document, I describe in detail the installation, configuration and
> use of my OpenStack cloud. I try to not use scripts to show clearly all the
> steps to follow.
>
> Installation is made on two physical servers and explanations are given to
> add more compute nodes.
>
> I added a lot of information, especially about the VLAN networking mode.
>
> Software Versions:
>
> - Operating System: Linux Ubuntu Server version 12.04 (Precise), 64 bits.
> - Cloud Computing: OpenStack version 2012.1 (Essex) including Nova,
> Glance, Keystone, and Horizon.
>
> Best regards,
>
> Eric
>
> __**_
> 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] [Doc] Documentation team meeting today

[Anne Gentle]

Hi all,
We're holding our monthly documentation meeting today, Monday May 14, 2012
at 2000 UTC (3:00 CST). The agenda can be found here:
http://wiki.openstack.org/Meetings/DocTeamMeeting

I've had a request to enable Skype for this meeting, which I'm amenable to.
We can use IRC for the meeting notes and for discussion as well.

Let me know if you have questions, and I'm looking forward to seeing you
there.
Anne
___
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] Error in documentation: Swift + Keystone + S3

[Anne Gentle]

Thanks for reporting, Philipp - doc bug logged and we'll get it taken care
of. https://bugs.launchpad.net/openstack-manuals/+bug/999655

Thanks Chmouel for confirming the correct settings.

Anne

Anne Gentle | http://justwriteclick.com/

[image: Facebook] <http://facebook.com/conversationandcommunity>[image:
Linkedin] <http://linkedin.com/annegentle>[image:
Twitter]<http://twitter.com/annegentle>


On Tue, May 15, 2012 at 4:22 AM, Philipp Wollermann <
wollermann_phil...@cyberagent.co.jp> wrote:

> Hi,
>
> today, I was trying to setup Swift with Keystone authentication and S3
> compatibility.
>
> Thanks to the very good documentation at http://swift.openstack.org/ and
> http://keystone.openstack.org/configuringservices.html I got a working
> setup quite fast, however S3 compatibility didn't work. The client couldn't
> authenticate, got a HTTP 500 error, which was caused by Keystone responding
> with a HTTP 404 to an internal request to /v2.0/s3tokens.
>
> After several hours, I found out, that no one ever mentions the small
> detail, that you have to include this in keystone.conf:
>
> [filter:s3_extension]
> paste.filter_factory = keystone.contrib.s3:S3Extension.factory
>
> and add "s3_extension" in the "[pipeline:admin_api]" section between
> "ec2_extension" and "crud_extension".
>
> As a user, that's nearly impossible to find out - try it using the
> documentation and Google. The only "official" place, where you can find it
> mentioned, is in the middle of the 81.5kb stack.sh inside devstack and
> you'll only find that, if you already know exactly what you're looking for
> :/
>
> I'm currently trying to get a CCLA signed by my company, if that succeeds,
> I'd like to contribute a fix to the docs. In the meantime, maybe that
> already helps someone. :)
>
> Best regards,
>
> --
> Philipp Wollermann
>
> Infrastructure Engineer
> CyberAgent, Inc. (Tokyo)
> https://github.com/philwo
>
>
>
> ___
> 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] [Doc] Starter docs and "articles"

[Anne Gentle]

Hi all -
I wanted to send a note out to discuss the growth of all the starter docs
and "articles" on a particular topic. Thanks all who are sending these to
the mailing list or tweeting 'em. We are listening.

The doc team has been discussing ways to ensure we help people find what
they seek while still getting high-quality content into the "official"
documentation. Here are some ideas. I'd like to get input from our wider
community as well.

What we're doing:

 - Add a "Where do I start?" section to the docs landing page. [1] Let us
know what you think of this approach. We discussed quite a bit a more
friendly approach to the docs site but I haven't identified a web dev and
designer to do the re-do, contact me if you're interested.
 - Reach out to writers and where licensing allows and something "official"
is not already documented, bring the content into the official docs. We've
done this a few times now, an example is [2].
 - Add link to blog entry to wiki page. [3]
 - Expand the install/deploy guide to include more distros so the "single
distro" guides can standalone. [4]
 - Hastexo has offered to write a separate HA guide, so we won't bring in
their 12.04 "all in one" install guide after all, since the CSS OSS guide
covers a similar scenario.
 - Remove "articles" from RST docs. (Currently nova only, let's discuss,
PTLs, look for a separate email and read more below.)
 - Add blog URLs to the Google Custom Search Engine at
http://docs.openstack.org. I took this as an action item from our last doc
team meeting. [5]

What we've discussed:

 - At the Design Summit, members of the nova core team asked for removal of
"article" style RST documents from the nova source repo, creating a more
doc-string based nova.openstack.org. Members of the swift core team, when
asked, did not want to go to this architecture. I haven't specifically
asked all the PTLs on this particular item. So there's still a potential
problem here of consistency, where to write what, and having all the
project.openstack.org sites that aren't really tied together. I don't have
a good solution to suggest just yet but know we're thinking about this
particular problem. One idea was to have devs want to write WordPress
"articles" and aggregate together, but we haven't found an ideal
implementation (design is fine, working code, not so much).
 - Setting up a separate WordPress blog for documentation only. Apparently
the aggregation tools just don't give us all the requirements for version
labels, bringing in one blog entry at a time (RSS feeds are needed), and so
on.
- Setting up a "support knowlege base" article site such as
http://support.mozilla.org. We discussed this at the last doc team meeting.
It seems to solve a lot of problems we have, but my current thinking (which
of course can change) is that a support KB is for troubleshooting articles,
while the "official" docs should create a happy path. These are two
different scenarios, and I'm pretty sure the docs team cannot take on the
support scenario with our current resources. A support knowledge base with
translation built-in will go a long way in supporting our growing base, so
this is important to me, but not in the Folsom plans currently.

I'll follow up with each PTL for the docstring discussion, and welcome all
input. Thanks for reading this far, and thanks for the docs.

Anne


1. https://review.openstack.org/#/c/7372/
2. https://review.openstack.org/#/c/7366/
3. http://wiki.openstack.org/BloggersTips
4. https://review.openstack.org/#/c/7431/
5.
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-14-19.59.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] Nova API Specification

[Anne Gentle]

Hi Phil -
An attempt at responses below, hopefully others can chime in where my
knowledge is limited. To answer an overarching (or is it underlying?)
question, the end goal is that the API descriptive specs are at
docs.openstack.org/api (even though some are named developer guides),
and the implementation in TryStack is documented at api.openstack.org.
Extensions are documented on api.openstack.org.

On Wed, May 30, 2012 at 8:33 AM, Day, Phil  wrote:
> Hi Folks,
>
> I was looking for the full definition of the API requests, and I’m a tad
> confused by what I find here:
>
> http://api.openstack.org/
>
> Specifically for Server Create there is both and “Server – Create” and
> “Server – Extended Create”, although as far as I can see the “extended
> create” isn’t actually an extension as such (the additional parameters are
> supported in the core servers module).
>
>

Extended Create is an extension as I understand it. When I query
TryStack I see {"updated": "2011-07-19T00:00:00+00:00", "name":
"Createserverext", "links": [], "namespace":
"https://docs.openstack.org/ext/createserverext/api/v1.1";, "alias":
"os-create-server-ext", "description": "Extended support to the Create
Server v1.1 API"}, {"updated": "2011-08-08T00:00:00+00:00",

So to me that means the action servers is extended but because it uses
the same action, it seems a part of core (and min_count and max_count
are required aren't they?). Brian Waldon can probably explain better
than I can.

>
> Also there seem to be a number of parameter values that aren’t specified in
> either interface entry, such as:
>
> min_count
>
> max_count
>
> networks
>
> key_name
>

I logged this as a doc bug:
https://bugs.launchpad.net/openstack-manuals/+bug/1006654

>
> So is the API document intended to be:
>
>
>
> -  A formal specification of the Interface
>
> -  A set of examples  (but if you want the details you need to read
> the code)
>

One of my goals going forward is crisper lines for docs about using
the APIs and docs describing the APIs. Users of the API should not
need to read Python code to use an OpenStack API. Thanks for your
observations.

Anne

___
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

[Anne Gentle]

Hi Nicolas -

I've got an update to the install document in review now, nearly
finished, that steps through both Ubuntu and CentOS. Please review:

https://review.openstack.org/#/c/7431/

The appendix contains all sample .conf and .ini files.

I'll send you a PDF to review separately. Your testing and input would
be very valuable to this effort.

Thanks,
Anne

On Thu, May 31, 2012 at 2:39 AM, Vogel Nicolas  wrote:
> Hi everybody,
>
>
>
> I’m 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 that’s 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 don’t 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.
>
>
>
> Thanks for the help,
>
> Best regards,
>
>
>
> Nicolas Vogel
>
>
>
> Collaborateur scientifique
> Institut ICT
> Route de Cheseaux 1
> 1400 Yverdon-les-Bains
> Tél. : (+41) 24 557 64 74
>
>
>
>
> ___
> 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] 401 Not Authorized from glance - How to fix ?

[Anne Gentle]

Several thoughts to ponder. One is, the nova image-list command is
using the Compute API, not the Image API. You can turn on --debug to
see the curl statement issued from the nova client (very handy, that).
Do:
nova --debug image-list
to see what I mean.

Also note there's a new bugfix for python-novaclient
(https://review.openstack.org/#/c/7200/) that fixes a problem with
prettyprint 0.6 removing printt (so it uses get_string now with the
latest version).

Also, I'd definitely point you to this guide as it has drop-in python
code for requesting a token:
http://docs.openstack.org/api/openstack-compute/programmer/content/using-python-to-obtain-the-authentication-token.html

Usually when I get an error from the Image API (Glance) it's because I
didn't put the proper paste-deploy filter in one of the Glance conf
files. If you're the cloud admin in this case, double-check your
glance config with:
http://docs.openstack.org/trunk/openstack-compute/install/content/configure-glance-files.html

If you're not the cloud admin, also know that the Image API isn't
publicly available on many public clouds such as TryStack.

Hope this is helpful.
Anne

On Fri, Jun 1, 2012 at 12:20 PM, Mandar Vaze / मंदार वझे
 wrote:
> Hi,
>
> I'm working on python program that needs to get images detail from glance.
> I was using "get_admin_context" earlier to do all the work in nova side, but
> this doesn't seem to work when I query glance.
> I get "401 Not Authorized" error.
>
> I think I need to get auth_token from keystone, and use it when creating
> RequestContext object - then glance query might work. (Is this assumption
> correct, in the first place)  But I do not know how to do this
> programatically, I looked at "nova image-list" command, but I didn't get
> clear picture on how this should be done.
>
> Can you point to any existing code that authenticates with keystone and then
> uses the auth-token to talk to glance ?
>
> Thanks,
> -Mandar
>
> ___
> 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] doc: "Reference for Configuration Options in nova.conf" shows up twice in the Compute Admin Manual

[Anne Gentle]

In a word, yes.

I noticed this yesterday but hadn't logged a bug about it, thanks Florian.

Anne

On Tue, Jun 5, 2012 at 4:38 AM, Florian Haas  wrote:
> Anne & fellow doc geeks,
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html
> http://docs.openstack.org/trunk/openstack-compute/admin/content/reference-for-options-in-nova-conf.html
>
> The former looks more current than the latter. Is
> compute-options-reference the correct place to submit patches to, and
> if so can the other one be removed?
>
> Cheers,
> Florian

___
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 API - Differences between API docs and code

[Anne Gentle]

Ah, great question Adrian. Ideally the PTL and I work together to
identify a resource to update the API guide prior to the release going
out. John and I spoke early on in the Folsom release timeframe about
potential API changes but then we didn't connect the dots that the
1.5.0 release needs API doc changes. Thanks for bringing it up.

The source for the API guides are housed in separate repos, in this
case it's at:

http://github.com/openstack/object-api

Anne

On Tue, Jun 5, 2012 at 2:18 PM, Adrian Smith  wrote:
> I've been digging about in the Swift codebase recently and I've come
> across a few few features that aren't documented in the API docs. For
> example, metadata at the account level, "prefix" parameter at the
> account level, "end_marker" parameter, object versioning (new in
> 1.5.0). These are just a few. I'm sure there are other examples.
> Should these features be included in the API docs (perhaps v2.0) or
> were they purposely left out? Obviously the code will continue to
> evolve but I'm curious what the situation is regarding the
> documentation.
>
> On a related note, where can I find the docbook source used to
> generate the Swift API documentation,
> http://docs.openstack.org/api/openstack-object-storage/1.0/content/index.html.
> I've looked around in the openstack-manuals project but can't seem to
> find anything.
>
> Thanks
>
> Adrian
>
> ___
> 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] [SOLVED] Re: "nova live-migration" failing on Ubuntu precise; libvirt live migration is OK

[Anne Gentle]

Absolutely should be mentioned in the docs - thanks for uncovering!

Anne Gentle
Content Stacker
a...@openstack.org


On Jun 9, 2012, at 1:49 PM, Florian Haas  wrote:

> On 06/07/12 14:21, Florian Haas wrote:
>> On Thu, Jun 7, 2012 at 9:53 AM, Thierry Carrez  wrote:
>>> Florian Haas wrote:
>>>> a few people have reported issues with live migration lately, and
>>>> I've been digging into them to narrow them down.
>>>> 
>>>> The symptom is relatively easy to describe: you run "nova live-migration
>>>>  ", and nothing happens.
>>>> [...]
>>>> I'd be thankful for any clues as to where to dig further.
>>> 
>>> You should submit a bug on the bugtracker about that, and continue the
>>> discussion there (pointing to the bug number from here)... I'd hate to
>>> see this one fall under the radar because it's not properly tracked.
>> 
>> Done: https://bugs.launchpad.net/nova/+bug/1009974
> 
> Apologies for the noise. I had mistakenly believed that since the list
> of --live_migration_flags contained spaces, it was OK to quote the
> --live_migration_* options. Evidently it's not, as removing the double
> quotes made the problem go away. My guests now do migrate.
> 
> Anne/Thierry: I've thus far been unable to find any documentation that
> says "don't use double quotes in nova.conf". In fact,
> http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html
> uses them in several places, including the --live_migration* flags. That
> quotes can break things appears to be a known issue as per
> https://bugs.launchpad.net/nova/+bug/987473. Is this something that we
> should mention in the documentation, or is this unexpected parser
> behavior that needs to get fixed?
> 
> Cheers,
> Florian
> 

___
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] Welcome RHEL/CentOS/Fedora to docland!

[Anne Gentle]

Hi all -
I just pushed through a couple of changes to the docs landing page and
added a brand new install/deploy guide for RHEL, CentOS, and Fedora.
Here's a summary:

1. The landing page links now point to /essex/ copies of the guides -
while the content is still identical to /trunk/, comments are enabled
on /essex/.
2. We now have two guides being built from the openstack-install
source - one for Ubuntu 12.04 (apt), one for RHEL, CentOS, and Fedora
(yum).
Ubuntu - http://docs.openstack.org/essex/openstack-compute/install/apt/content/
RHEL/CentOS/Fedora -
http://docs.openstack.org/essex/openstack-compute/install/yum/content/

I've logged a cleanup bug on the yum one already -
https://bugs.launchpad.net/openstack-manuals/+bug/1010163.
Also the cover page won't indicate which one is which until this build
bug is fixed - https://bugs.launchpad.net/openstack-manuals/+bug/1008579.

Of course we couldn't have done it without the help of our reviewers -
huge props to Lorin Hochstein, Razique Mahroua, Pádraig Brady, Nicolas
Vogel, and Tom Fifield for continually checking the reviews.

Collaborators welcome - and all the collaborators so far are much appreciated.

Thanks,
Anne

___
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] [Docs] Doc team meeting today 2000 UTC

[Anne Gentle]

Hi all -
Feel free to join us on IRC and Skype for a doc team meeting scheduled
for today, Monday June 11, 2012, 2000 UTC (3:00 CST). Here's the
agenda as listed at http://wiki.openstack.org/Meetings/DocTeamMeeting.

Action items from the last meeting
Nova config flags reviews
Landing page switched from trunk to Essex links (still a problem
with PDF download from Essex install/deploy guide)

Please review new High Availability guide introduction at
https://review.openstack.org/#/c/8139/
Blueprints status
Operations manual
Deployment template
API "try-it-out"
metadata in docs - to know where source is, to quickly edit
source eventually
Doc tools update
Setting language to zh should work in PDF builds now

New tricks -  processing instruction for a break in a
table cell for example
Don't use a -SNAPSHOT in a pom.xml, always use releases
Open discussion

Thanks,
Anne

___
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] Welcome RHEL/CentOS/Fedora to docland!

[Anne Gentle]

Yep, what Pádraig said. :)

Anne Gentle
Content Stacker
a...@openstack.org


On Jun 12, 2012, at 6:35 AM, Pádraig Brady  wrote:

> On 06/12/2012 10:59 AM, Rajesh Avula wrote:
>> Hi Anne,
>> 
>> I am unable to open the link,  
>> http://docs.openstack.org/essex/openstack-compute/install/apt/content/
>> RHEL/CentOS/Fedora 
>> <http://docs.openstack.org/essex/openstack-compute/install/apt/content/%0ARHEL/CentOS/Fedora>
> 
> Your mail client is messing up those I think.
> Anyway the correct ones are:
> 
> ¹ http://docs.openstack.org/essex/openstack-compute/install/apt/content/
> 
> ² http://docs.openstack.org/essex/openstack-compute/install/yum/content/
> 
> ¹ Ubuntu
> ² RHEL/Centos/Fedora
> 
> 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

Re: [Openstack] Swift API Documentation Reviews

[Anne Gentle]

Thanks Chmouel for reviewing. I am reviewing (and patching as needed) also.

Adrian, the API will not version upwards until the API itself is
redesigned, so the doc will remain an API 1.0 document.

Generally speaking, the documents stored in object-api, compute-api,
identity-api, netconn-api and image-api repos will document the code
that's in a core project. Changes in them need to be approved by core
members of the corresponding project, and doc-core can also approve
small changes to get them published.

Thanks,

Anne



On Thu, Jun 14, 2012 at 6:16 AM, Chmouel Boudjnah  wrote:
> On Tue, Jun 12, 2012 at 9:16 AM,   wrote:
>> For anyone interested in documentation I've posted two changes in relation 
>> to the Swift API docs,
>> Describe the end_marker parameter (https://review.openstack.org/#/c/8375/)
>> Added section on metadata at account level 
>> (https://review.openstack.org/#/c/8374/)
>
> Nice, thanks you, I have done some review. How does it work for docs
> does it need to have two core doing a +2 or one is enough?
>
>> Since the API documents are versioned (currently 1.0) is it right to 
>> retrospectively update them now? Is the documentation a spec and Swift an 
>> implementation of that spec or are the two running in parallel?
>
> I'd say the two running in parallel.
>
>> There are a few other gaps in the API docs but I wanted to get clarification 
>> before proceeding.
>
> Thanks,
> Chmouel.

___
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] glance_api_servers vs. glance_host vs. keystone?

[Anne Gentle]

Hi Lars -

Sounds like you're really looking for a conceptual understanding and I
like that! Keystone does maintain the service catalog, and the Image
service (glance) needs specific entries. See
http://docs.openstack.org/essex/openstack-compute/install/yum/content/keystone-concepts.html.

I believe glance_host and glance_port are deprecated and not needed in
an Essex installation, use only glance_api_servers in the nova.conf.

Gabe has good answers for your previous questions - and hopefully you
can reference this page for Qpid configuration information:
http://docs.openstack.org/essex/openstack-compute/admin/content/configuration-qpid.html

Anne

On Fri, Jun 15, 2012 at 3:26 PM, Lars Kellogg-Stedman
 wrote:
> Well, apologies for the stupid subject line.  In the interests of
> sewing as much confusion as possible, here's the question that was
> supposed to go along with that subject:
>
> nova.conf appears to sport several configuration options related to
> glance, including:
>
> - glance_host
> - glance_port
> - glance_api_servers
>
> These seem suspiciously similar.  Do they do the same thing?  And
> shouldn't this information actually come from Keystone, in which there
> is an endpoint registered for the glance service?
>
> --
> Lars Kellogg-Stedman        |
> Senior Technologist                                | 
> http://ac.seas.harvard.edu/
> Academic Computing                                 | 
> http://code.seas.harvard.edu/
> Harvard School of Engineering and Applied Sciences |
>
> ___
> 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] Translation and Internationalization in OpenStack

[Anne Gentle]

Hi Daisy -

Thanks for all the work.

A couple of questions:
I thought the plan was to start with install guide(s) only? It looks
like you brought in all the openstack-manuals repository as resources.
I'd prefer just
https://www.transifex.net/projects/p/openstack-manuals-i18n/resource/openstack-install/
and /common to be the resources for starters.

Was this content brought in from the stable/essex or master branch?
How can a translator know which branch the source is from?

How will updates to the English version of the manuals get into
Transifex? Is there a "freeze date" the English authors need to be
aware of?

Are you interested in presenting your translation methods at the APEC
conference in Beijing in August? See http://openstack.csdn.net/. We
definitely want to make this effort well known.

All potential translators on this mailing list, please let us know
your thoughts on this approach - both the tooling and starting with
the install guide only. We build for you!

Thanks,
Anne


On Wed, Jun 20, 2012 at 3:54 AM, Ying Chun Guo  wrote:
> Hi, Gabriel
>
> Are there any progress or updates with the translation management tools?
>
> I tried to slice the manuals into pieces and uploaded the templates to
> Transifex.
> I also tried to enable Transifex in the Git repository. All things run well.
> I will vote for Transifex now.
>
> You can try my current effort here:
> https://www.transifex.net/projects/p/openstack-manuals-i18n/resources/
>
> and welcome for suggestions.
>
> Regards
> Daisy
>
> openstack-bounces+guoyingc=cn.ibm@lists.launchpad.net wrote on
> 05/09/2012 06:15:59 AM:
>
>> Gabriel Hurley 
>> Sent by: openstack-bounces+guoyingc=cn.ibm@lists.launchpad.net
>>
>> 05/09/2012 06:15 AM
>>
>> To
>>
>> Ryan Lane ,
>>
>> cc
>>
>> "openstack@lists.launchpad.net" 
>
>
>>
>> Subject
>>
>> Re: [Openstack] Translation and Internationalization in OpenStack
>>
>> Hi Ryan,
>>
>> Thanks for pointing me to TranslateWiki. I'm more than happy to add
>> more tools to the comparison matrix to make sure we make the best choice!
>>
>> I've updated the matrix:
>>
>> https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-
>> ErDUdFgzT3VNVXQxd095bFgzODRmajJDeVE
>>
>> At a glance TranslateWiki falls somewhere in the middle, with my
>> biggest concern being the recommended method for re-integrating the
>> translation files into the origin repositories. Other issues stood
>> out as well, but that one was the biggest.
>>
>> As a reminder, the features listed there are not of equal weight, so
>> having more "red" doesn't necessarily rule any solution out if it's
>> "green" in critical areas another is lacking. If you think I've
>> misjudged anything, feel free to let me know.
>>
>> All the best,
>>
>>     - Gabriel
>>
>> > -Original Message-
>> > From: Ryan Lane [mailto:rl...@wikimedia.org]
>> > Sent: Tuesday, May 08, 2012 2:09 PM
>> > To: Gabriel Hurley
>> > Cc: openstack@lists.launchpad.net
>> > Subject: Re: [Openstack] Translation and Internationalization in
>> > OpenStack
>> >
>> > > Tools
>> > > 
>> > >
>> > > I know people have strong feelings and concerns on which tools are
>> > > best
>> > and which features matter most, so I've put together a comparison
>> > matrix.
>> > >
>> > > https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-
>> > ErDUdFgzT3VNVXQxd
>> > > 095bFgzODRmajJDeVE
>> > >
>> > > It features our current solution (Launchpad) and the top two
>> > > contenders
>> > people have asked me to look at (Pootle and Transifex). The list of
>> > features
>> > for comparison contains the concerns voiced at the summit session, those
>> > voiced by the community to me, those voiced by the infrastructure team,
>> > and my own experience working on translations for other open source
>> > projects (such as Django).
>> > >
>> > > Having worked with all three tools, I would strongly suggest
>> > > Transifex,
>> > particularly given that we as a community have to do almost no work to
>> > maintain it, it's the only tool that supports OpenStack as a
>> "project hub" with
>> > shared teams and management, and it offers us a strong crowdsourced
>> > translation community.
>> > >
>> >
>> > You should also consider translatewiki (translatewiki.org). It's used
>> > for a
>> > number of very large projects (MediaWiki and extensions used on
>> > Wikimedia
>> > sites, OpenStreetMap, etc), and it has a large and active translator
>> > community. For example, MediaWiki is very actively translated in 100
>> > languages, and has translation for roughly 350 languages total.
>> >
>> > The translatewiki people are interested in hosting OpenStack since
>> > Wikimedia Foundation is using OpenStack products, and translatewiki
>> > cares
>> > deeply about our language support. In fact, they were the first people
>> > to
>> > complain about nova's broken utf8 support, which prompted us to push in
>> > fixes.
>> >
>> > - Ryan
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~open

Re: [Openstack] How to use Cloudpipe

[Anne Gentle]

The docs team is on it!

https://bugs.launchpad.net/openstack-manuals/+bug/1015937

I <3 the docs team.

Anne

On Thu, Jun 21, 2012 at 3:00 AM, Sébastien Han  wrote:
> Hi,
>
> The official doc needs to be updated at some points. If you want to make
> this compatible with Ubuntu 12.04.
> You can check my article
> here http://www.sebastien-han.fr/blog/2012/06/20/setup-cloud-pipe-vpn-in-openstack/
> and the fork of the mirantis
> repo https://github.com/leseb/cloudpipe-image-auto-creation/blob/master/cloudpipeconf.sh
>
> I will also try to  update the OpenStacj wiki asap.
>
> Cheers.
>
>
> On Thu, Jun 21, 2012 at 7:01 AM, Atul Jha  wrote:
>>
>> Hi Naveen,
>> 
>> From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net
>> [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of
>> Naveen Kuna [naveen.k...@oneconvergence.com]
>> Sent: Thursday, June 21, 2012 8:22 AM
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] How to use Cloudpipe
>>
>> Hi All,
>>
>> Can anyone help me in making cloudpipe image and how to use cloudpipe
>> image for VPN service ?
>>
>>
>> http://docs.openstack.org/trunk/openstack-compute/admin/content/cloudpipe-per-project-vpns.html
>>
>> Please go through documentation pages next time onwards before asking
>> questions which are already easily available.
>>
>> Thanks in Advance
>>
>> Regards,
>> Naveen
>>
>> Cheers!!
>>
>> Atul
>> 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
>
>
>
> ___
> 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] Adding docs gating jobs?

[Anne Gentle]

Sounds good to me. Mo working doc builds, mo betta.

Anne Gentle
Content Stacker
a...@openstack.org

On Tue, Jun 26, 2012 at 9:02 AM, Monty Taylor  wrote:
> Hey guys!
>
> We have all of the projects properly and consistently building and
> uploading sphinx docs from in tree. This is pretty exciting, because it
> means one more resource we can expect to work.
>
> So related to that, we were talking about putting in a gating job for
> each project to prevent changes from breaking the docs. I don't really
> expect these jobs to fail builds very often, as the jobs themselves are
> pretty stable - but obviously it's the kind of thing people might have
> an opinion on.
>
> Thoughts?
> Monty
>
> ___
> 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] Call for proposals for linux.conf.au 2013

[Anne Gentle]

Hi all -

July 6th is the deadline for proposals related to open source for
linux.conf.au 2013. See http://linux.conf.au/cfp for more info. There
are three ways to present:

Presentations
Presentations are 40 minute slots that are generally presented in
lecture format. These form the bulk of the available conference slots.
Tutorials
Tutorials are 90 minutes that are generally presented in a
classroom format. They should be interactive or hands-on in nature.
Tutorials are expected to have a specific learning outcome for
attendees.
Miniconferences
Miniconfs are day-long sessions on a specific topic.

Happy info sharing!
Anne

___
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] [Docs] new "DocImpact" notifier flag

[Anne Gentle]

Hi all -

Greetings from sunny-with-intermittent-thunderstorms Ohio! I wanted to
let you all know of a new way to integrate docs with the development
process - the DocImpact flag. Thanks to the CI team's diligence, you
can now add "DocImpact" to your commit messages, anywhere in the
message, and changes with "DocImpact" in their commit messages
automatically send an email to the openstack-doc-core team with a link
to the review site as soon as the patch set is pushed to Gerrit.

I'd like you to use this flag in these cases:
1. You're pushing a commit with documentation contained in the patch set.
2. You're pushing a commit with a new option or change in the default
option or default behavior.
3. You're pushing a commit with a new feature that requires
documentation. Ideally you'll work with the doc team to figure out a
doc plan.

Sending a commit with this flag doesn't guarantee doc will be written
- but it does enable us to prioritize the incoming changes. Generally,
I don't want this flag to be used to throw a doc task over a wall,
there are no walls here, we're all in this together. :)

Thanks CI team (Clark Boylan especially) for the assist.

Anne

P.S. I'm on vacation this week - but I will add this flag usage to the
HACKING file when I get back (unless someone wants to beat me to 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom

[Anne Gentle]

All,

Just wanted to note that either decision means a revision and addition
of documentation - to me, one option does not create more doc need
than the other. Removal or deprecation, both require documentation.

Anne

On Wed, Jul 11, 2012 at 11:22 AM, Narayan Desai  wrote:
> I also vote for option 1, but the migration path really needs to be
> solid and well documented.
>  -nld
>
> On Wed, Jul 11, 2012 at 10:52 AM, Andrew Clay Shafer
>  wrote:
>> One vote for option 1.
>>
>> Remove Volumes
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Doc] New openstack-docs list

[Anne Gentle]

Now with the new fabulous mailing list server and the help of Duncan
McGreggor, we have a real mailing list for anyone interested in
OpenStack docs.

To subscribe, go to:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

Originally we had a group at https://launchpad.net/~openstack-doc - if
you're in that group I'd love for you to subscribe to the new mailing
list.

This list will get the notifications for DocImpact flags as well.

Thanks,
Anne

___
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] Proposal for Sean Dague to join nova-core

[Anne Gentle]

I agree, especially after seeing how thorough Sean is. I'm not on
nova-core myself but wanted to give a thumbs up to his nomination.

On Fri, Jul 20, 2012 at 12:49 PM, Vishvananda Ishaya
 wrote:
> Hello Everyone,
>
> When I was going through the list of reviewers to see who would be good for 
> nova-core a few days ago, I left one out. Sean has been doing a lot of 
> reviews lately[1] and did the refactor and cleanup of the driver loading 
> code. I think he would also be a great addition to nova-core.
>
> Vish
>
> [1] https://review.openstack.org/#/dashboard/2750
> ___
> 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] Ceph performance as volume & image store?

[Anne Gentle]

I don't know if it will confirm or correlate with your findings, but
do take a look at this blog post with benchmarks in one of the last
sections:

http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/

I'm trying to determine what parts should go into the OpenStack
documentation, please let me know if the post is useful to you in your
setting and what sections are most valuable.
Thanks,
Anne


On Tue, Jul 24, 2012 at 6:08 PM, Josh Durgin  wrote:
> On 07/23/2012 08:24 PM, Jonathan Proulx wrote:
>>
>> Hi All,
>>
>> I've been looking at Ceph as a storage back end.  I'm running a
>> research cluster and while people need to use it and want it 24x7 I
>> don't need as many nines as a commercial customer facing service does
>> so I think I'm OK with the current maturity level as far as that goes,
>> but I have less of a sense of how far along performance is.
>>
>> My OpenStack deployment is 768 cores across 64 physical hosts which
>> I'd like to double in the next 12 months.  What it's used for is
>> widely varying and hard to classify some uses are hundreds of tiny
>> nodes others are looking to monopolize the biggest physical system
>> they can get.  I think most really heavy IO currently goes to our NAS
>> servers rather than through nova-volumes but that could change.
>>
>> Anyone using ceph at that scale (or preferably larger)?  Does it keep
>> up if you keep throwing hardware at it?  My proof of concept ceph
>> cluster on crappy salvaged hardware has proved the concept to me but
>> has (unsurprisingly) crappy salvaged performance. Trying to get a
>> sense of what performance expectations I should have given decent
>> hardware before I decide if I should buy decent hardware for it...
>>
>> Thanks,
>> -Jon
>
>
> Hi Jon,
>
> You might be interested in Jim Schutt's numbers on better hardware:
>
> http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/7487
>
> You'll probably get more response on the ceph mailing list though.
>
> 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

___
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] Suspend/Stop VM

[Anne Gentle]

As I noted on Twitter, there's an open doc bug at
https://bugs.launchpad.net/openstack-manuals/+bug/1029560 noting this
gap. Thanks George for clicking through to say it impacts you.

I'm sending a second email to the mailing list next to discuss this
unfortunate gap in reality in the API docs, what I believe the causes
to be, and how I'd like to move forward.

Thanks,
Anne



On Mon, Jul 30, 2012 at 11:13 AM, George Reese
 wrote:
> Thanks, but I am looking for how this is done via API.
>
> -George
>
> On Jul 30, 2012, at 11:11 AM, Pengjun Pan  wrote:
>
> I never tried to stop a VM using api. But run a "nova help", it has
> pause, reboot, resume, etc.
>
> To bypass nova api, you can use virsh to stop instances. Do a "sudo
> virsh list --all", it will list all the running instances even if nova
> cannot see it for some reason. And then you can kill all the "ghost"
> instances by "sudo virsh shutdown ".
>
> Hope this helps.
>
> PJ
>
>
> On Mon, Jul 30, 2012 at 10:50 AM, George Reese
>  wrote:
>
> I must be missing something, but I can't find any docs on how to suspend or
> stop a VM via API.
>
> Any pointers, please? :)
>
> -George
>
> --
> George Reese - Chief Technology Officer, enStratus
> e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
> +1.207.956.0217
> enStratus: Enterprise Cloud Management - @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
>
>
> --
> George Reese - Chief Technology Officer, enStratus
> e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
> +1.207.956.0217
> enStratus: Enterprise Cloud Management - @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
>

___
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] API docs - spec and dev guide split proposal

[Anne Gentle]

Hi again all, your friendly doc coordinator here.

I'd like to get a big push towards documenting reality instead of
relying only on the specs stored in the compute-api repository. As an
example, recently a Rackspace writer inserted min_count and max_count
to the compute-api repository but the change was reversed after a
request by Brian Waldon and Jorge Williams to leave the spec as-is. I
agree that the spec has value but I believe we need to push towards
reality and creating developer guides.

So what I'd like to propose here is that we govern these repos as
specs and change the titles of those documents to API specification:

compute-api
image-api
identity-api
object-api
netconn-api

At the same time, we'd start new "developer guides" in the
openstack-manuals repository that document reality. We can track the
work needed through the openstack-manuals bug and blueprint system.

I went up to Brian Aker after his keynote at OSCon seeking contacts at
HP who are interested in doing this type of work, and I have started
some one-on-one meetings, but I'd like to find more interested
collaborators. Anyone at Rightscale or Enstratus interested? Also are
there other API implementers who are experts in how the APIs really
work? Please join in finding the right solution here.

Does this proposal sound like a workable solution? Any tweaks or other
suggestions?

Thanks,
Anne

___
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] Create multiple instances in one request

[Anne Gentle]

These were documented but then pulled out because min_count and
max_count are not to spec.

We are now working on a cleanup effort described at
http://wiki.openstack.org/DisableServerExtensions.

It seems the log from the last Nova meeting where this was discussed
is gathered together with the QA team meeting due to the meetbot not
being turned off between meetings.

The log is here, scroll to the bottom to read.
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-17.00.log.html

Hope this is helpful - though cleanup will be the most helpful, please
feel free to join in the effort. :)
Anne

On Tue, Aug 7, 2012 at 1:13 PM, David Kranz  wrote:
> It is a little strange but the following seems to be true.
>
> 1. The nova HTTP API has a max_count and min_count that go in the request
> dictionary.
> 2. This is not documented.
> 3. The novaclient python api create function has these arguments.
> 4. The novaclient cli does not have them, or at least they are not
> documented by 'nova help boot'.
>
> Beats me why this is the case...
>
>  -David
>
>
> On 8/7/2012 1:47 PM, Patrick Petit wrote:
>
> Dear All,
>
> Looking into the details of the request_spec part of a RPC message ensuing a
> nova boot command.
> There is a 'num_instances' : 1 property that implies the value could be
> different than one (default) even though there is no cardinality parameter
> in nova boot nor in the API (unless I missed something big). So, I am
> curious to know: why is it there if we cannot create more than one instance
> at a time through the API, but more importantly is there a (secret) way to
> set that value different than 1 to tell the scheduler "please create
> multiple instances of that type".
> Thanks in advance
> Patrick
>
>
>
> ___
> 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] Help with meta-data

[Anne Gentle]

All, sorry for top posting, but this is a fine example of why we
really need bloggers to help with the documentation. These fragmented
instructions are difficult to rely on - we need maintainable,
process-oriented treatment of content.

Mirantis peeps, you have added in your blog entries to the docs in the
past, let's find ways to continually do that and maintain going
forward.

I'm not so interested in more install guides, but definitely
interested in more configuration guides. So Kord, while I like the
idea (and execution!) of the StackGeek 10-minute guide, it's not one
to bring into the official docs. But we would definitely welcome your
reviews of incoming updates to the docs!

Thanks Simon for bringing your difficulties to the list - we
continually work on improving the docs. What you learn now could help
hundreds if not thousands of others, so I'd love for you to improve
the official docs with your findings.
Thanks,
Anne

On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter  wrote:
>
> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>
>> On Aug 8, 2012, at 8:20 PM, "Simon Walter"  wrote:
>>
>>>
>>> On 08/09/2012 06:45 AM, Jay Pipes
>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>> key to be able to ssh into the VM, which apparently is supplied by the
>>> meta-data service.
>>>
>> use cirros.
>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>
>
> Thank you. That was good advice.
>
> Somehow I was not able to connect via ssh. I managed to get novnc working
> and logged into the VM. I can't find anything about connecting via serial or
> the like as you can with Xen. I need to read more about KVM I guess.
>
> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
> install would be the quickest way to get and running. Now I find myself
> pouring over documentation trying to understand how best to setup
> FlatDHCPManager with two network interfaces. I understand many things have
> changed. So I don't want to go reading something out of date. I found these
> blog posts which explained a lot:
> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
> But am I reading the wrong thing? I like the way Stackgeek had it set up:
> http://stackgeek.com/guides/gettingstarted.html
>
> But I think they are missing details or it's out dated. For example, with
> their setup the vnc console in horizon does not work because nova-vncproxy
> is installed rather than novnc.
>
> I'm pretty sure I can figure the networking out if I have the right
> documentation in the first place. Is there a clear instructions for this
> anywhere? Or would someone mind walking me through it again. So far I've
> followed the stackgeek setup above, but the networking is obviously stuffed.
>
> Must I have the flat_interface in promiscuous mode?
> Or does it actually need an IP address?
> Why are my VMs picking up an IP address from the public_interface DHCP
> server and not from the flat_network_bridge?
>
> Too many questions to ask. So I thought I should just ask: what is missing
> or incorrect from Stackgeeks 10 minute scripts?
>
> Many thanks for any advice, tips, docs, etc.
>
>
> Cheers,
>
> Simon
>
>
> --
> simonsmicrophone.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

___
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] Help with meta-data

[Anne Gentle]

Hi Eugene -
But I thought "everyone" was on the openstack list! :) Thanks for following up.

On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov  wrote:
> Hi Anne,
>
> I accidentally found this email of yours while looking for links to my post.
> I'd probably have found it earlier if you cc'd me on
> ekirpic...@gmail.com or ekirpic...@mirantis.com [yes, that's two
> different spellings...] :)
>
> I support the idea that this should be somehow integrated in the docs,
> but I'm not sure where exactly in the docs is a good place for
> information of this style. Would it help if I just linked to the posts
> from some wiki page or from the docs?

I do like to put relevant blog posts on the wiki at
http://wiki.openstack.org/BloggersTips, so you can certainly add to
that page. If it's really missing information in the docs, though, it
should be added to the docs. I know that's a tough judgement call but
we all have to encourage that call.

Or would it only help if I (or
> somebody) actually merged the relevant parts of the posts into
> official documentation?

I wouldn't say "only help" but I prefer that you merge the relevant
parts of the posts. It's tougher for a doc team member to merge only
parts in without violating the license of the content - you as content
owner can certainly choose which parts to move into the official
documentation though.

Thanks for asking for clarifications - these are certainly gray areas
that I'd like to shine light upon.
Anne

> On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle  wrote:
>> All, sorry for top posting, but this is a fine example of why we
>> really need bloggers to help with the documentation. These fragmented
>> instructions are difficult to rely on - we need maintainable,
>> process-oriented treatment of content.
>>
>> Mirantis peeps, you have added in your blog entries to the docs in the
>> past, let's find ways to continually do that and maintain going
>> forward.
>>
>> I'm not so interested in more install guides, but definitely
>> interested in more configuration guides. So Kord, while I like the
>> idea (and execution!) of the StackGeek 10-minute guide, it's not one
>> to bring into the official docs. But we would definitely welcome your
>> reviews of incoming updates to the docs!
>>
>> Thanks Simon for bringing your difficulties to the list - we
>> continually work on improving the docs. What you learn now could help
>> hundreds if not thousands of others, so I'd love for you to improve
>> the official docs with your findings.
>> Thanks,
>> Anne
>>
>> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter  wrote:
>>>
>>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>>
>>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter"  wrote:
>>>>
>>>>>
>>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>>> meta-data service.
>>>>>
>>>> use cirros.
>>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>>
>>>
>>> Thank you. That was good advice.
>>>
>>> Somehow I was not able to connect via ssh. I managed to get novnc working
>>> and logged into the VM. I can't find anything about connecting via serial or
>>> the like as you can with Xen. I need to read more about KVM I guess.
>>>
>>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>>> install would be the quickest way to get and running. Now I find myself
>>> pouring over documentation trying to understand how best to setup
>>> FlatDHCPManager with two network interfaces. I understand many things have
>>> changed. So I don't want to go reading something out of date. I found these
>>> blog posts which explained a lot:
>>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>>> http://stackgeek.com/guides/gettingstarted.html
>>>
>>> But I think they are missing details or it's out dated. For example, with
>>> their setup the vnc console in horizon does not work because nova-vncproxy
>>> is installed rather than novnc.
>>>
>>> I'm pretty sure I can figure the netwo

Re: [Openstack] 回复： 回复： Openstack Folsom 2 or 3

[Anne Gentle]

The FAQ [1] covers this scenario (installing a specific release with
DevStack) for a stable branch. I think this is how you install with
milestone-proposed branch. However not all projects have a
milestone-proposed branch yet.

Open and edit localrc, then run stack.sh. Swift is on its own release
schedule so pick a tag in the Swift repo that is just before the
milestone release. For example:

GLANCE_BRANCH=milestone-proposed (doesn't exist)
HORIZON_BRANCH=milestone-proposed (doesn't exist)
KEYSTONE_BRANCH=milestone-proposed
NOVA_BRANCH=milestone-proposed
QUANTUM_BRANCH=milestone-proposed (doesn't exist)
SWIFT_BRANCH=1.6.0 (guessing as it's the "just before the
milestone release release)

Can anyone confirm?
Thanks,
Anne

1. http://devstack.org/faq.html



On Fri, Aug 17, 2012 at 3:43 AM, Trinath Somanchi
 wrote:
> Hi -
>
> Thanks for the reply...
>
> Will there be any Installation help for bringing up Openstack using the
> Folsom-3 release on Fresh Ubuntu 12.04 LTS Server Machine.
>
> Kindly share with me the installation help.
>
> Thanking you all
>
> --
> Trinath
>
>
> On Fri, Aug 17, 2012 at 1:23 PM, Aaron Rosen  wrote:
>>
>> By far in my opinion the easiest route to take in order to quickly try out
>> and play with the latest code is www.devstack.org.
>>
>> Aaron
>>
>>
>> On Fri, Aug 17, 2012 at 3:17 AM, Salvatore Orlando 
>> wrote:
>>>
>>> Hi,
>>>
>>> Folsom-3 is going to be released this evening GMT. Expect it to be
>>> available after 1700 GMT.
>>> You'll find both a folsom-3 tag on github, as well as tarballs
>>> downloadable from launchpad.
>>>
>>> Regards,
>>> Salvatore
>>>
>>>
>>> On 17 August 2012 08:50, 延生 付  wrote:

 Seems not release yet. Hold on :)


 Regards,


 willfu
 发件人： Trinath Somanchi 
 收件人： 延生 付 
 抄送： "openstack@lists.launchpad.net" 
 发送日期： 2012年8月17日, 星期五, 下午 2:25
 主题: Re: 回复： [Openstack] Openstack Folsom 2 or 3

 Hi-

 Thanks for the reply.

 How to download the Folsom-3 code base of Openstack... Can you guide me
 on this...

 Thanking you...

 --\
 Trinath


 On Fri, Aug 17, 2012 at 11:47 AM, 延生 付  wrote:

 Try this one for folsom 2.

 https://github.com/openstack/nova/tree/folsom-2

 All the source is under https://github.com/openstack

 You can choose the required version.

 Regards,
 willfu
 发件人： Trinath Somanchi 
 收件人： openstack@lists.launchpad.net
 发送日期： 2012年8月17日, 星期五, 下午 12:59
 主题: [Openstack] Openstack Folsom 2 or 3

 Hi-

 I want to download the Openstack Folsom 2 or 3. Is Version 3
 downloadable.

 My web search is not fruitful with the the link to the download of the
 release.

 Please guide me on downloading Openstack Folsom - 3 or 2 source code.

 thanking you,

 --
 Regards,
 --
 Trinath Somanchi,
 +91 9866 235 130


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to: openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help  : https://help.launchpad.net/ListHelp





 --
 Regards,
 --
 Trinath Somanchi,
 +91 9866 235 130




 ___
 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
>>>
>>
>
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> 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] [Docs] It's that time of the release!

[Anne Gentle]

Hi all -
Now that we're in feature freeze period, it's a great time to look at
what docs are needed for Folsom. You can help with documentation in
several ways. Here are some ideas.

_Review docs_
Go to review.openstack.org and review open patches on
openstack-manuals. Daily, hourly, weekly, any cadence will help. We
should be approving lots of changes quickly and patching patches to
get as much truth out there as we can. [1]

_Write API docs and samples_
There are several doc bugs opened to enhance Compute API docs:
Reboot, soft reboot: https://bugs.launchpad.net/openstack-manuals/+bug/1017543
os-quotas admin extension:
https://bugs.launchpad.net/openstack-manuals/+bug/1029567
os-aggregates missing info:
https://bugs.launchpad.net/openstack-manuals/+bug/1015821
Pause, suspend missing info:
https://bugs.launchpad.net/openstack-manuals/+bug/1029560
server_diagnostics undocumented:
https://bugs.launchpad.net/openstack-manuals/+bug/1035483
deferred_delete undocumented:
https://bugs.launchpad.net/openstack-manuals/+bug/1035484
missing server_id in metadata call:
https://bugs.launchpad.net/openstack-manuals/+bug/1035491
migration missing information:
https://bugs.launchpad.net/openstack-manuals/+bug/1022653

_Write API tests for samples_
Vish has a patchset for a templatized test integration for API
samples, please help:
https://review.openstack.org/#/c/11263/

_New landing pages_
I've proposed a partial patch to update the landing pages, please
review and enhance as you see fit.
https://review.openstack.org/#/c/11232/

_Work on a Comprehensive CLI guide_
Starting point is here: https://review.openstack.org/#/c/11274/

_Make migration better to document_
One bug in particular points out how hard it is to understand live
migration and migration. [2] Please review
https://review.openstack.org/#/c/11172/ and analyze whether a name
change would help? Not sure if it's in the realm of FFE but even good
docs can't help much when the command is a misnomer.

_Work on an Operations Manual_
See [3] for the blueprint and an outline. We've been discussing on the
openstack-doc list too. [4]

_Fix doc bugs_
See [5] for the list of doc bugs, assign yourself, propose a patch,
change the world. Do it again.

If a team is interested in a doc sprint day, I'd be happy to organize,
recruit, and write. Let me know.

PTLs, I believe I've been in touch with all of you for your "doc plan"
for the release, but definitely reach out for clarity!

Thanks,
Anne


1. 
https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z
2. https://bugs.launchpad.net/openstack-manuals/+bug/1022653
3. 
https://blueprints.launchpad.net/openstack-manuals/+spec/openstack-operations-manual
4. http://lists.openstack.org/pipermail/openstack-docs/2012-August/51.html
5. https://bugs.launchpad.net/openstack-manuals

___
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] Documentation help on Folsom -3 Milestone

[Anne Gentle]

Hi Trinath -

Could you be more specific about your needs? Documentation for Folsom is an
ongoing effort and the docs do not track to milestone releases. Are there
specific areas like networking or volumes or computing that you are wanting
to validate and configure?

To run "milestone-proposed" branches using Devstack, you can edit the
stackrc file prior to running the stack.sh script to point to specific repo
branches of each project. See http://devstack.org/stackrc.html.

Anne

On Tue, Aug 28, 2012 at 1:43 AM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:

> Hi-
>
> Do we have any documentation help in configuration and validation of
> Openstack Folsom - 3 milestone?
>
> Please help me in this regard.
>
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> 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] [Docs] What's Up Doc August 29 2012

[Anne Gentle]

Hi all -
Here's a weekly report from docs land. Thanks for reading!

tl;dr - Summarizes the doc activities and related news of the past week.

1. In review and merged this past week:
Quantum API guide v2.0 now merged, build job created, still needs to
be linked from API landing page
CLI guide now builds, still needs to be linked in
Compute admin extensions additions
os-aggregates additions
os-hypervisors in review
separation of compute troubleshooting from object storage troubleshooting
live migration updates
multinic updates
PowerVM docs added
Features section added to Object Storage doc
Updates to nova.conf - but still more work to be done, now over 500
options (was 467)

2. High priority doc work:
We're now at 27 open High priority doc bugs targeted for Folsom
(https://bugs.launchpad.net/openstack-manuals/+milestone/folsom). We
can do it! Two are in review now.
A couple of big ones:
 - Quantum needs integration in the Compute Admin guide
(https://bugs.launchpad.net/openstack-manuals/+bug/1043241)

3. Doc work going on that I know of:
Diane Fleming has completed a proof-of-concept for content sharing for
API guides so that OpenStack content can be repurposed for service
providers like Rackspace and HP.
Quantum has an outline for their Admin manual at
https://bugs.launchpad.net/openstack-manuals/+bug/1043177. Please join
in their efforts.

4. New incoming doc requests:
The mailing list thread about migration has been very useful. I had
originally asked Razique to document his experience going from Diablo
to Essex (tracked with
https://bugs.launchpad.net/openstack-manuals/+bug/967402), but as he
explained it wasn't a "typical" migration. I don't think there is a
typical migration, but I'd like a section in the docs discussing
migration. Ryan Lane's message to the list is a good starting point.
We also have a task for essex to folsom migrations:
https://bugs.launchpad.net/openstack-manuals/+bug/1043032

5. Doc tools updates:
The doc tools team picked up three bugs related to doc builds:
- 1036237, API site only builds on clouddocs maven plugin version 1.2.0.
- 1008581, Output a useful message when the maven plugin tries to
build from docbook4 source
- 1008579, Output meaning phrase for cover page of PDF when using
conditional phrases in the title
The full tagged list is here if anyone has an interest:
https://bugs.launchpad.net/openstack-manuals/+bugs?&field.tag=doc-builds

6. Other doc news:
The Design Summit is just six weeks away! We have three 40-minute
slots in the Documentation Track and next week (around Sept. 7th) the
proposal site opens. I'd love to hear proposals for documentation
blueprints and discussions.

The newly formed OpenStack Foundation board had an agenda item to
discuss a new license for the documentation. I haven't heard the
outcome, but the proposal is to use a CC-By license for documentation
since it is easier to understand a Creative Commons license for docs
rather than try to apply Apache2 licensing to contributed content.

I got good feedback on Twitter from @matt2000 that I'm working on
incorporating for a clearer path to downloads, install instructions,
to configuration. It won't be a quick fix, but it's related to the
review I have as WIP here: https://review.openstack.org/#/c/11232/.
Reviews requested.

Please let me know if you have any questions.
Anne

___
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] Openstack NOVA and Metadata.

[Anne Gentle]

>> Though I have too many questions, I'm in need of these since, Want to
>> understand the ROLE of metadata concept?
>
>
> The role is simple - you can set metadata on a server, and retrieve it later
> if you wish.

Let's say you're creating a web interface, like a dashboard, that
talks to the Compute API. You might want to let your users assign
"tags" to their servers like "LAMP" or "WAMP" or "production" or
"testarea" - metadata could be used for that use case.

Hope this helps.
Anne

___
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] A few posts on H/A OpenStack

[Anne Gentle]

Hi Eugene  -

Nice posts. If you're interested in collaborating on a new H/A
document, Florian started one in the docs repository at
https://github.com/openstack/openstack-manuals/tree/master/doc/src/docbkx/openstack-ha
written in asciidoc, automatically publishing, but not yet linked on
the docs site. It needs more "meat" and your posts could bring some
"meat" - what do you think about bringing them in to enhance the
guide?

Thanks,
Anne

On Fri, Aug 31, 2012 at 5:59 PM, Eugene Kirpichov  wrote:
> Hi,
>
> Thought the community could be interested. We (Mirantis) recently
> published a few posts about building H/A OpenStack.
>
> http://www.mirantis.com/blog/intro-to-openstack-in-production/ - Intro
> http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/ -
> MySQL and RabbitMQ
> http://www.mirantis.com/blog/software-high-availability-load-balancing-openstack-cloud-api-servic/
> - API services
>
> Comments very welcome.
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov
>
> ___
> 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 bindings for ... PHP?

[Anne Gentle]

Glen Campbell is working on a PHP library here (and would welcome
reviewers I'm sure).

https://github.com/rackspacedrg/raxsdk-php/blob/master/docs/userguide/index.md

On Mon, Sep 3, 2012 at 1:07 AM, Tom Fifield  wrote:
> Hi all,
>
> I've been handed an interesting piece of PaaS software (its various pieces
> are in Java, PHP, python and bash!) and told "make it work with OpenStack".
>
> Noone's done any work to make nova play with PHP, have they?
>
>
> Regards,
>
>
> Tom
>
> ___
> 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] [Docs] Progress this week 9/6/12

[Anne Gentle]

Hi all -
Here's the latest status on doc work ongoing. With all the interest
showed over the holiday weekend here in the states, I had expected a
few more patches to be submitted, but they didn't materialize. That
said, the Quantum team has a great draft going for a Quantum admin
guide, and we've had updates to the api.openstack.org site, so we keep
moving forward. Operator docs sorely needed!

1. In review and merged this past week:
Adds os-hypervisors doc for api site.
Cleanup on compute server create for api site.
Update os-networks extension document for api site.
Getting Started text updated for Folsom.
Old references to Austin, Bexar, Cactus, and Diablo releases removed.

2. High priority doc work:
There are still 22 doc bugs targeted for folsom and marked high -
please pick up a bug from this list:
https://launchpad.net/openstack-manuals/+milestone/folsom
Many are Compute API related. I'd like to get the tested samples into
the api.openstack.org site, can someone help with that?

Also needed:
Migration information - even an outline of a known migration process
will be helpful.
https://bugs.launchpad.net/openstack-manuals/+bug/1043032
Sample nova.conf files -
https://bugs.launchpad.net/openstack-manuals/+bug/1041703

3. Doc work going on that I know of:
The Image API v2.0 draft is nearly complete with a doc build process
nearly complete to go with it.
Dan and the Quantum team are working on an admin guide for Quantum.
Object versioning and static web ready for merging into object-api.

4. New incoming doc requests:
Still need volume documents to go along with all the drivers. These
should go into the Compute Admin Manual in the openstack-manuals
repository.
Have asked Mirantis's Piotr to bring in his monitoring post about Compute.
Asked the CI team to set up a new openstack/volume-api repo so we can
put a spec document in it to document the Volume API beyond just
api.openstack.org.

5. Doc tools updates:
Working on lessening the image not found errors when building.

6. Other doc news:
Followed up with the Pearson editor to seek guidance on a CC license
for the operations manual. I expect an answer tomorrow so we can keep
moving forward on that book.

___
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] [Doc] Documentation/Web meeting 2100 UTC today

[Anne Gentle]

In about an hour, join us on IRC in #openstack-meeting to discuss
documentation. An agenda is available at
http://wiki.openstack.org/Meetings/DocTeamMeeting.

You should be SO updated with my weekly updates that you don't even
need to attend! Just kidding, all are welcome and encouraged to attend
and bring your doc questions.

Thanks,
Anne

___
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] [Doc] Documentation/Web meeting 2100 UTC today - actually 2000

[Anne Gentle]

My apologies, the UTC time is 2000. In Google calendar I trust. :)

Anne

On Mon, Sep 10, 2012 at 2:01 PM, Anne Gentle  wrote:
> In about an hour, join us on IRC in #openstack-meeting to discuss
> documentation. An agenda is available at
> http://wiki.openstack.org/Meetings/DocTeamMeeting.
>
> You should be SO updated with my weekly updates that you don't even
> need to attend! Just kidding, all are welcome and encouraged to attend
> and bring your doc questions.
>
> Thanks,
> Anne

___
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] [Doc] This week in Docs 9/12/12

[Anne Gentle]

Wow, we went from 34 High folsom-targeted doc bugs two weeks ago to 17
on Monday. Great work everyone. I think there might be something to
this community documentation thing. :-P Tom Fifield and Ying Chun Guo
(Daisy) are tearing it up with reviews and patches!

Still over 100 doc bugs (some are tasks) to be worked. Here's the
summary for this week.

1. In review and merged this past week:
Object Storage API dev guide now contains object versioning and static
web information.
Add swift name_check filter to docs.
Add retry host cost weight function to scheduler docs.
Remove ArchFilter, adds ImagePropertiesFilter.
Extended section on overloading ldap attrs.
Add GET (show) to OS API keypairs extension docs.
Add the network association api docs.
Add Network creation to OS API docs.

Reviews still needed:
The Compute extensions for createBackup, os-migrateLive, and
os-resetState api for api.openstack.org.
https://review.openstack.org/#/c/12857/
The CLI user guide has been updated with Quantum information.
https://review.openstack.org/#/c/12851/
A glossary has been added that now builds properly.
https://review.openstack.org/#/c/12707/

2. High priority doc work:
Please pick up a bug from this list:
https://launchpad.net/openstack-manuals/+milestone/folsom

I'd like to get the tested samples that are going into nova into
the api.openstack.org site, can someone help with that?

Quantum is working diligently on their API guide and Admin guide so
you can install and run Quantum. Sounds like lots of people want this,
I'd like the focus on the official docs, but unoffficial docs are fine
too of course.

3. Doc work going on that I know of:
I'm working on new landing pages and navigation for the docs and api
sites. Please take a look at https://review.openstack.org/#/c/11232/
to see the work in progress.
David Hendler is working with John Griffith to finalize a Volume API
developer guide (a spec, more or less).
Bug fixes and more bug fixes. We're still at 111 doc bugs, all have
been reviewed and triaged, so jump in.

4. New incoming doc requests:
Need help with https://review.openstack.org/#/c/12214/ on the CI
puppet scripts to get the Image API 2.0 draft published.

5. Doc tools updates:
Think these are the doc tools bugs that the tools team is working on
this sprint:
http://bit.ly/Q9eGsu

6. Other doc news:
We've got two proposals for the Documentation Track at the Design
Summit and I'd like more! Please propose at
http://summit.openstack.org.

I've done a summary spreadsheet of what API docs live where at
https://docs.google.com/a/justwriteclick.com/spreadsheet/ccc?key=0Ar7TiePyvTNVdFhGVTZCSzRQQzJCYWtNZnZXblV6aUE#gid=0
titled OpenStack API Docs - What lives where? It should be a good
reference for which specs have what types of information (WADL? XSD?
DocBook? Markdown? RST?) all answers are here.

We met this week for our monthly doc meeting.
Summary: 
http://eavesdrop.openstack.org/meetings/doc_web_meeting/2012/doc_web_meeting.2012-09-10-20.01.html

Meeting Log: 
http://eavesdrop.openstack.org/meetings/doc_web_meeting/2012/doc_web_meeting.2012-09-10-20.01.log.html

Thanks,
Anne

___
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] TRYSTACK DOWN TIME AND RUNTIME ERRORS!!!

[Anne Gentle]

I also want to chime in that TryStack is an important first experience
with OpenStack so we're working on the issue to get it resolved and
get TryStack on track!
Anne

On Fri, Sep 14, 2012 at 9:03 AM, Syed Armani  wrote:
>
>
> Thanks for the quick response Nachi :)
>
> Cheers!
> Syed
>
>
> On Fri, Sep 14, 2012 at 6:49 PM, Nachi Ueno  wrote:
>>
>> Hi Syed
>>
>> Sorry for inconvenience.
>> Recent several website down is due to misconfiguration of Apache.
>> Some proxy settings looks wrong, so IMO this is not problem of OpenStack
>> itself.
>> I'll fix this issue ASAP.
>>
>> Thank you for your notice
>> Nachi Ueno
>>
>> 2012/9/14 Syed Armani :
>> >
>> > Hi,
>> >
>> > Most of the people who come to try OpenStack via trystack.org  have
>> > started
>> > complaining that trystack is down most of the times. The first
>> > impression
>> > they draw from this is that "MAY BE OPENSTACK IS UNRELIABLE". This is
>> > creating a false impression on the people who want to try openstack.
>> > https://www.facebook.com/groups/269238013145112/
>> >
>> > Cheers!
>> > Syed Armani
>
>

___
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] [Docs] review request: new landing pages

[Anne Gentle]

Hi all -
I've completed all the re-writes for new landing pages for
docs.openstack.org. I'd like more reviewers at
https://review.openstack.org/#/c/11232/ to make sure I didn't miss
anything and that the links all work. I'm purposely leaving the
/essex/index.html untouched in order to make this new design for
Folsom and current.

The idea is to provide a simpler top page and have the drill-downs
specific to audiences, with URLs that should indicate the category of
information.

I want to do more work to integrate api.openstack.org to eliminate
confusion about "what's more current, api.openstack.org or
docs.openstack.org?" But that can be in another patch or set of
patches. One thing we really, really need, is better navigation on
api.openstack.org through a drop-down menu for nav such as the "Jump
to" drop down on https://dev.twitter.com/docs/api. If anyone would
like to mock it up (probably css and javascript) I'd gladly integrate
it.

Thanks, all.
Anne

___
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] TC candidacy

[Anne Gentle]

I'd like to propose myself as a Technical Committee candidate for one
of the open seats in the current election.

==Background and Experience==
Hi, I'm Anne Gentle, I work at Rackspace serving as the OpenStack doc
coordinator. I put "Content Stacker" on my business cards to point out
the power of content coming from many people and many projects that I
happily stack into organized sites. I maintain the docs.openstack.org
and api.openstack.org site by running the documentation project like a
code project, with blueprints, bugs, and task tracking. Also
documentation is published continuously and automatically with reviews
in the Gerrit system like code. I've been working on OpenStack for two
years. Here's a link to my contributed patches and reviews on Gerrit.
https://review.openstack.org/#/q/reviewer:anne%2540openstack.org,n,z

My open source experience precedes my OpenStack history. Starting
around 2008, I worked with FLOSS Manuals writing open source manuals
for open source software, http://flossmanuals.net. I'm always
researching the latest tools, techniques, and limited amount of
academic research available about open source and documentation. This
year I released a 2nd edition of my book, Conversation and Community:
The Social Web for Documentation that includes a chapter about open
source and documentation. It's a unique field and I'm quite drawn to
it.

==Technical Expertise==
I've been working on technical documentation in software and IT and
have built a unique perspective through the years on how to integrate
documentation closely with fast-moving code. I also have the technical
knowledge and user perspective for consuming OpenStack APIs. I'm a
fast learner and open to many tools and processes related to code and
docs.

OpenStack affords us all opportunities to design, implement,
experiment, and build upon documentation and I enjoy working with the
community to continually improve the documentation. Thanks for your
consideration.

Anne Gentle
---
http://justwriteclick.com
http://www.linkedin.com/in/annegentle

___
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] [Docs] What's Up Doc? September 19 2012

[Anne Gentle]

Hi all -
Here's the weekly report from docs land. Thanks for reading!

tl;dr - Still over 100 doc bugs, 18 targeted for folsom, 11 of those
18 do not have assignees. New docs landing pages from
https://review.openstack.org/#/c/11232/ should land this week or next
prior to the release date.

1. In review and merged this past week:
Hyper-V documentation now included in the Hypervisors chapter of the
Compute Admin guide. Nice teamwork and tenacity Peter and gang.
Document VMs with disks stored in LVM.
Fixes to Compute API docs for security group update and keypair
example correction.
Links to CLI guide for nova.
Link to Quantum API 2.0 guide from API docs landing page.
Glossary now available at
http://docs.openstack.org/glossary/content/glossary.html

Please review:
Instance Management chapter shaping up nicely:
https://review.openstack.org/#/c/12533/
In about a week or less, the landing pages will change with this
patch: https://review.openstack.org/#/c/11232/. Please review to weigh
in on the new design.
Brought in tested Compute API samples for api.openstack.org here:
https://review.openstack.org/#/c/13201/
Cloudpipe documentation for Folsom: https://review.openstack.org/#/c/13281/
Essex nova.conf example files: https://review.openstack.org/#/c/13157/
Addition of os-server-diagnostics extension doc:
https://review.openstack.org/#/c/13280/
Cover XenServer configurations for Migration:
https://review.openstack.org/#/c/13202/

2. High priority doc work:
Networking admin information being brought in, please review
Volumes admin information, please update existing for folsom
Configuration information: need to determine if all nova.conf options
are in the folsom
documentation.https://bugs.launchpad.net/openstack-manuals/+bug/1052978.
Hypervisor and scheduler information: Hypervisors can now co-exist --
update docs https://bugs.launchpad.net/openstack-manuals/+bug/1048879

3. Doc work going on that I know of:
Diane Fleming is bringing the Quantum Admin manual into the
openstack-manuals repository this week.
David Hendler has asked John Griffith to review the Volume API 1.0
spec for bringing into the new volume-api repository.
Dolph M is working on a markdown version of the Identity API 3.0
document to bring it into the Gerrit workflow process.

4. New incoming doc requests:
"Just" everything targeted for Folsom. Insert maniacal laugh here.

5. Doc tools updates:
Testing in progress for the doc tools bugs that the tools team is working on
this sprint, see http://bit.ly/Q9eGsu for the list.

6. Other doc news:
Still seeking proposals for the Documentation Track at the Design
Summit - go to http://summit.openstack.org to propose your awesome doc
topic for discussion. While it looks like there are two proposed, one
of the proposers can't attend, so I'm definitely seeking more.

___
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] TryStack latest status

[Anne Gentle]

Hi all -

We're taking small steps to get the TryStack experience back on track.

Yesterday we moved the trystack.org site to Rackspace hosting rather
than on an Apache server on the Cloud Controller and enabled SSL on
that site. That move should keep the site up and the content is
updated to set expectations on the latest, which is:
- The ARM zone, running Essex code, is the only available TryStack
installation. Both the Essex and Diablo zones (x86) have been closed
for maintenance.
- Request access to the ARM zone using this form: http://eepurl.com/nGEzj.

The next step is to get an x86 zone back up, running Folsom code.
- SwiftStack has offered to help with deploying an Object Storage
installation on TryStack. Thanks Joe and John!
- Nachi Ueno would like assistance with deploying Compute, Image, and
Identity on TryStack. Contact him to help. Great opportunity to get
some ops chops!

Thanks for your patience while we continue to work through repeatable,
managed processes to make TryStack run predictably.

Anne and Nachi

___
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 v2.0 dev API doc confusion

[Anne Gentle]

Hi Boden -
This is a known bug with the way those Keystone dev docs are output.
I'm tracking it here:
https://bugs.launchpad.net/openstack-manuals/+bug/1015119

I can help someone fix this - thanks for pointing it out again. Please
vote on that bug to raise its visibility to get it attention.

Thanks,
Anne

On Fri, Sep 21, 2012 at 3:53 AM, boden  wrote:
> I came across the following Keystone dev API docs:
> http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
> This set of keystone v2.0 docs includes documented APIs for operations
> such as 'List Roles for User on Tenant', 'Check Token', etc.. I tried a
> few of these APIs on some recent code from master -- works as documented.
>
> However if I follow the typical API doc links: www.openstack.org >
> Documentation > API Documentation > OpenStack Identity Service Developer
> Guide API 2.0, I end up at the following location:
> http://docs.openstack.org/api/openstack-identity-service/2.0/content/
> This page does not contain a number of the documented APIs from the 1st
> link I posted. For example no info on 'List Roles for User on Tenant',
> 'Check Token', etc..
>
> Can someone help me understand which version of the documented APIs are
> current (supported) for Folsom? I'm thinking maybe the 1st doc link I
> posted is being created for folsom, but is not yet "live".
>
> Thanks much
>
>
> ___
> 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] Please provide the step by step guide for 3 node swift instalation steps

[Anne Gentle]

Hi John -
Thanks for asking more specific questions. You'll find that you need
to follow the entire installation guide in order to get all the
components working together. To specifically answer your questions,
though, I'll paste some HTML links rather than the whole PDF.

The names of packages for nova can be found here:
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-the-cloud-controller.html
Example architectures for Compute (nova) are here:
http://docs.openstack.org/trunk/openstack-compute/admin/content/example-installation-architecture.html

Swift installation via packages is documented here:
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/general-installation-steps-swift.html
Example architecture for Object Storage (swift) is here:
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/example-object-storage-installation-architecture.html

Hope these are helpful.
Anne

On Fri, Sep 21, 2012 at 1:46 AM, John Raja  wrote:
> from where i can download the package for nova and swift
>
>
> 
> Regards,
> John Raja
> Ip Extn  :- 509028
> Tel:- 022-40609028
>
>
>
>
> On Tue, Sep 18, 2012 at 12:22 PM, John Raja 
> wrote:
>>
>> Please provide the step by step guide for 3 node swift instalation steps .
>>
>>
>>
>> 
>> Regards,
>> John Raja
>> Ip Extn  :- 509028
>> Tel:- 022-40609028
>>
>>
>
>
> ___
> 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] [Docs] Documentation set for Folsom

[Anne Gentle]

Hi Patrick -

The Quantum admin guide in its current state is publishing here:
http://docs.openstack.org/trunk/openstack-network/admin/content/

You can review the ongoing work here:
https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z

For documentation, we typically keep the "master" branch publishing to
docs.openstack.org/trunk/ and will cut a docs.openstack.org/folsom/
set of documents about a month after the software release.

Hope this is helpful -
Anne

On Tue, Sep 25, 2012 at 10:16 AM, Patrick Petit
 wrote:
> Hi There,
>
> Can someone tell me what is current plan regarding the release of the
> documentation set for Folsom?
> Of particular interest is the admin guide extension covering Quantum.
> Thanks
> Patrick
>
> ___
> 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] Script to boot servers

[Anne Gentle]

Hi Guillermo -

The CLI guide was recently added. It's a bit rough and needs
improvement but here are links you can use to answer your questions.

On Tue, Sep 25, 2012 at 1:42 PM, Guillermo Alvarado
 wrote:
> Hi Everyone,
>
> I want to make a script that create tenants, users and boot a server. Where
> I can found documentation of the nova python client?

http://docs.openstack.org/cli/quick-start/content/index.html#nova-cli-refrence

> Anybody knows the class/method to boot servers and the params?

nova image-list
nova flavor-list
nova boot

See
http://docs.openstack.org/cli/quick-start/content/index.html#launch_instance

> Thanks And Regards.
>
> ~GA
>
> ___
> 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] Script to boot servers

[Anne Gentle]

For python-specific calls, see for example:

http://docs.openstack.org/developer/python-novaclient/ref/servers.html



On Tue, Sep 25, 2012 at 2:11 PM, Anne Gentle  wrote:
> Hi Guillermo -
>
> The CLI guide was recently added. It's a bit rough and needs
> improvement but here are links you can use to answer your questions.
>
> On Tue, Sep 25, 2012 at 1:42 PM, Guillermo Alvarado
>  wrote:
>> Hi Everyone,
>>
>> I want to make a script that create tenants, users and boot a server. Where
>> I can found documentation of the nova python client?
>
> http://docs.openstack.org/cli/quick-start/content/index.html#nova-cli-refrence
>
>> Anybody knows the class/method to boot servers and the params?
>
> nova image-list
> nova flavor-list
> nova boot
>
> See
> http://docs.openstack.org/cli/quick-start/content/index.html#launch_instance
>
>> Thanks And Regards.
>>
>> ~GA
>>
>> ___
>> 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] What's up doc? September 26 2012

[Anne Gentle]

Summary: We're down to 14 doc bugs targeted to Folsom but still want your help!

After Thursday's code release, I will meet with Thierry to get ideas
for how to scientifically determine a good doc release date based on
the bug/task list. Stay tuned for that.

I have instructions for how to do a docs release at
http://wiki.openstack.org/Documentation/Release. In case I am hit by a
bus or otherwise rendered useless, I pledge to keep this page updated.

1. In review and merged this past week:
Lots of exclamation marks here because I was wowed this past week a
few times. Nice work Stackers!
New landing pages for docs.openstack.org!
Tons of new entries in the Glossary, thank you Josh Turgasen! Email me
a mailing address and I will send really a nice OpenStack gift. I mean
it!
New Quantum Admin guide!
Great new section on XenServer configurations for Migration!

In review: VNC proxy diagram: https://review.openstack.org/#/c/13634/

In review: all-in-one Folsom install https://review.openstack.org/#/c/13713/

2. High priority doc work:
Definitely need more volumes doc updates, John mentioned the need in
his cinder weekly meeting.

Restructuring the source and builds for api.openstack.org with the end
result of redirecting from docs.openstack.org/api to
api.openstack.org. Any questions? Here's the plan.
https://etherpad.openstack.org/api-site-structure

Here are some doc tasks we'd like help with:
Task: Document how to configure Keystone with SSL
Task: Document keystone middleware situation in operator docs
Task: Update Ubuntu install/deploy guide to explain the Cloud Archive
Task: Add information about scaling out additional volume nodes for Compute

3. Doc work going on that I know of:
John Griffith to populate volume-api repo with an API spec.

4. New incoming doc requests:
Ongoing fixes to pom.xml and builds.
Need to get working builds for Identity API and Image API specs.

5. Doc tools updates:
The Clouddocs maven plugin has a few fixes coming in soon, perhaps
this month, but we'll update our pom.xmls to pick these up after the
release. Here's the ones we want:
- Automatically handle images:
Detects if images are missing from a document and fail if an
image is missing. You can turn off this validation by setting
false in your pom.xml.
For Webhelp output, automatically converts .svg to .png.
Automatically copies images to the Webhelp output directory.
- Automatically build pdf when building webhelp and copy pdf to
webhelp directory unless false is set in your
pom.xml.
-  Provide better error messages if incorrect DocBook version is used
(i.e. if DocBook 4.x is used instead of 5.x). Fixes bug
https://bugs.launchpad.net/openstack-manuals/+bug/1008581.
-  Move profiling to early in the pipeline. This fixes bugs where
content in title and revhistory weren't being profiled, such as
https://bugs.launchpad.net/openstack-manuals/+bug/1008579.
- Fix bug where IDREFs weren't validated. (Might fix
https://bugs.launchpad.net/openstack-manuals/+bug/1031374).

6. Other doc news:
Still seeking one additional topic proposal for the Summit - I will
fill it with "Grizzly doc planning" if no one else has a burning doc
discussion need. Also would it be useful to have a docs user test area
in the Developer lounge? I'd love to set that up. And, do we want to
have a doc meetup at one of the lunch tables at the Summit? Let me
know.

___
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] [Docs] Documentation set for Folsom

[Anne Gentle]

Hello Vibhu -

Apologies for a delayed response. I'm having trouble automatically
publishing the Image API specs right now.
Here is the 1.1 API spec for the Image service (glance).

http://docs.openstack.org/api/openstack-image-service/1.1/content/

Thanks,
Anne


On Wed, Sep 26, 2012 at 4:46 PM, Bontala, Vibhuvardhan
 wrote:
> Hi Anne,
>
> Do you have a similar pointer to the Image Service for Folsom? I am 
> interested in the API reference specifically.
>
> Thanks
> Vibhu
>
> -Original Message-
> From: openstack-bounces+vibhuvardhan.bontala=emc@lists.launchpad.net 
> [mailto:openstack-bounces+vibhuvardhan.bontala=emc@lists.launchpad.net] 
> On Behalf Of Anne Gentle
> Sent: Tuesday, September 25, 2012 11:40 AM
> To: Patrick Petit
> Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
> Subject: Re: [Openstack] [Docs] Documentation set for Folsom
>
> Hi Patrick -
>
> The Quantum admin guide in its current state is publishing here:
> http://docs.openstack.org/trunk/openstack-network/admin/content/
>
> You can review the ongoing work here:
> https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z
>
> For documentation, we typically keep the "master" branch publishing to
> docs.openstack.org/trunk/ and will cut a docs.openstack.org/folsom/
> set of documents about a month after the software release.
>
> Hope this is helpful -
> Anne
>
> On Tue, Sep 25, 2012 at 10:16 AM, Patrick Petit
>  wrote:
>> Hi There,
>>
>> Can someone tell me what is current plan regarding the release of the
>> documentation set for Folsom?
>> Of particular interest is the admin guide extension covering Quantum.
>> Thanks
>> Patrick
>>
>> ___
>> 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] Doc on nova-volume

[Anne Gentle]

Hi Ahmed -

Some thoughts below.

On Wed, Sep 26, 2012 at 4:49 PM, Ahmed Al-Mehdi  wrote:
> Hello,
>
> I recently setup an OpenStack environment using two servers.  I read-up the
> document "Object Storage Administration Guide" at the OpenStack site.  I
> have two questions:
>  - I love the first few chapters of this document that talks about
> conceptual parts of a cloud OS, and then maps the components in it to what
> is provided by OpenStack.  However, this document refers to the "Cactus"
> release.  Is there an updated document for the Essex release  (containing
> similar chapters)?

I believe the only reference to "Cactus" in the Object Storage Admin
Guide is that Glance has been stable since Cactus. Please re-read the
sections starting here:
For folsom: 
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/logical-architecture.html

For essex: 
http://docs.openstack.org/essex/openstack-object-storage/admin/content/logical-architecture.html

>  - I am trying to understand (detail wise) the difference in services
> provided by swift (object store) and nova-volume.  For example, if I wanted
> to provide storage/volumes/LUNs via FCoE, should I be pretty much focusing
> on the "nova-volume" module.

Object Storage is Swift, Block storage is Cinder as of the Folsom
release. Please read:
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/overview-block-storage-arch.html

We don't yet have a separate "Block Storage" Admin guide to point to.

Hope this helps.
Anne

>
> Any pointers to documents would be most appreciated.
>
> Thank you,
> Ahmed.
>
>
>
> ___
> 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