Image location is fixed and the redirects are also in. Note that the
redirects are set up for https://wiki.openstack.org, so they aren't
currently testable (though I did manually change the redirect temporarily
to test it). The redirects have the following behavior:
wiki.openstack.org/Article -
On Wed, Dec 19, 2012 at 2:27 AM, Daniel P. Berrange berra...@redhat.comwrote:
The migration has not handled 'BR' syntax that Moin uses to
insert line breaks. This causes a bit of a mess, eg look at
the Things to avoid when creating commits section here
On Wed, Dec 19, 2012 at 10:18 AM, Nicolas Barcet nico...@barcet.com wrote:
At first glance, the Ceilometer main page [1] lost from [2]:
* last column from each table
* colors in tables
* did not convert macro Navigation(children,1) to list sub pages
[1]
On Wed, Dec 19, 2012 at 10:57 AM, Ryan Lane rl...@wikimedia.org wrote:
My vote is to edit the pages to fix them. The conversion script is a giant
hideous mess of perl. Overall I think we'll be able to fix most issues
quickly in a doc sprint by editing the pages.
for Navigation(children,1) we
The most obvious issue is how ugly the new main page is :) The loss of
image inclusion and columns transformed an admittedly not perfect page
(disclaimer: I authored it) into something unreadable and very
unwelcoming. Note that it's probably the only page that uses column
layout, so maybe we
On Tue, Dec 18, 2012 at 2:21 AM, John Garbutt john.garb...@citrix.comwrote:
One more thing I spotted around links.
In the migrated wiki:
[[XenServer/DevStack|XenServer and [[DevStack
Clearly it's a simple fix to this:
[[XenServer/DevStack|XenServer and DevStack]]
I guess this extra
I've just finished importing the content from the MoinMoin wiki into the
MediaWiki instance. Please check the content:
https://wiki-staging.openstack.org/wiki/Main_Page
We're using a self-signed certificate for now. We are ordering a proper
certificate, but eve that cert will still appear
There aren't any code examples in the wiki that I know of. If you have
examples we can certainly find a way to indicate Apache 2.0 for code, I
don't find this problematic.
Yeah, we can wrap a source lang=python/source block in a template
that also adds in license text for any code. Should be
On Sat, Nov 17, 2012 at 3:05 AM, Laurence Miao laurence.m...@gmail.comwrote:
Hi Michael,
I'd love to do something to make this wiki better, if I could.
Do we have any doc/wiki task force to coordinate all the document stuff
about OpenStack?
It would be smooth/easy to have a team take care
Of the As, Option A1 in particular is my preference.
However, I've heard a lot of talk about people wanting a users and
operators list to be merged -- with enough support for that, I would
be happy with Option B.
+1
Do we have information on the type/number of discussions that are
user
On Mon, Sep 3, 2012 at 8:53 AM, Anne Gentle a...@openstack.org wrote:
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
There's also a fairly Wikimedia-specific and incomplete
Yesterday I spent the day finally upgrading my nova infrastructure
from diablo to essex. I've upgraded from bexar to cactus, and cactus
to diablo, and now diablo to essex. Every single upgrade is becoming
more and more difficult. It's not getting easier, at all. Here's some
of the issues I ran
There was talk of trying to set up test infrastructure that would roll out
Essex and then upgrade it to Folsom in some automated fashion so we could
start learning where it breaks. Was there any forward momentum on that?
This would be awesome. Wrapping automated tests around upgrades would
It would be fascinating (for me at least :)) to know the upgrade
process you use - how many stages you use, do you have multiple
regions and use one/some as canaries? Does the downtime required to do
an upgrade affect you? Do you run skewed versions (e.g. folsom nova,
essex glance) or do you
On Mon, Aug 20, 2012 at 1:52 PM, pat p...@xvalheru.org wrote:
Hello,
I'm new to this list and OpenStack at all. I want to ask a question: I want to
ask if it's possible to use one LDAP per tenant. I've searched the web, but
didn't found the answer.
In keystone this is not currently
We have submitted a patch https://review.openstack.org/#/c/11086/ to address
https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha that simplifies
recovery from a node failure by introducing an API that recreates an
instance on *another* host (similar to the existing instance 'rebuild'
On Thu, Aug 2, 2012 at 1:23 PM, Mitchell Broome
mitchell.bro...@gmail.com wrote:
I'm using essex 2012.1 and I'm running into an issue with tenant
separation using the ec2 api. I end up having to give a user the
'admin' role in keytone to create instances within a tenant. I can
live with that
I do wonder if it would make sense to gather user feedback and goals before
the summit, like the day (or week) before, to help provide some priorities
(from their perspective) to consider going into the summit.
This does seem valuable, although keep in mind that most users are a release
You can use a token to get a token. Look at the authenticate code in
keystone/service.py
Have the user initially get a non-tenant specific token. Pass that in the
x-auth header to POST /tokens/ along with a tenantid and you will get a new
one scoped to the tenant
Ah. This is perfect,
I'm working on upgrading to essex, which means I need to start using
keystone. My use case seems to not fit keystone very well, though...
In my environment, one user can be a member of many projects (some
users are in up to 20-30 projects). Management of projects is done
nearly completely though
Not in Essex. When we discussed the Domains blueprint, one issue that I
brought up was nested groups/projects. That would solve your problem. It
is not currently being developed.
Ok. I can deal with handling tens of thousands of tokens, but I need
some way to ensure a user doesn't need to
I haven't been thinking about quotas, so bear with me here. A few thoughts:
Certain deployments might not be able to touch the LDAP backend. I am
thinking specifically where there is a corporate AD/LDAP server. I tried to
keep the scheme dependency simple enough that it could be layered
So, I should wait until L3 and try again, but in quantum?
Yes, from talking to Vish a while back, the plan is that nova-network will
be more less feature frozen, with new features targeting Quantum. We're
at a bit of an awkward transition point right now, so probably best to
continue to
L3 + Floating IPs are being added to Quantum in F-3 (got bumped from F-2).
So, I should wait until L3 and try again, but in quantum?
I haven't looked at your patch in detail, but it seems like you're looking
to notice when a floating-ip is allocated or deallocated, and use that to
trigger a
I'm trying to add support to nova for BGP announcements for floating
IP addresses (as an alternative to subnetting and ARP). The change
currently has a -1, since networking code is moving to quantum. It
seems that quantum doesn't have floating IP support, though. Where
should I be adding this
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-ErDUdFgzT3VNVXQxd095bFgzODRmajJDeVE
It features our current solution
According to the statement of this article from Gartner
group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a
highly immature platform.
But why? What's make Openstack so immature?
Any comments on that?
Thank you
On Thu, Feb 9, 2012 at 3:29 AM, Adam Young ayo...@redhat.com wrote:
I've made some strides in the KSL LDAP implementation. I've set up a
github clone with the code pushed:
https://github.com/admiyo/keystone/tree/ldap
The code is ugly, as I'm in Just get it working mode. Cleanup will
Sorry for the slow response on this. There has been a lot to do for e-3. In
any case, here are my thoughts on the subject. I am really not convinced that
configuration management needs to be part of nova at all. This is stuff that
should be built on top of nova. We have a bit of work to
what's best for
OpenStack.
Agreed. It may be that some form of hook system, or some other way of
extending nova without hacking core would be a more appropriate way of
handling things like this. Of course, an extensions system also makes
compatibility between vendors much more difficult.
- Ryan
to run. My provider
should automatically detect the hardware failure and re-launch my
instance on another piece of hardware; it should also notify me that
it happened, but that's a different story ;).
- Ryan Lane
___
Mailing list: https://launchpad.net
.
- Ryan Lane
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On Tue, Sep 27, 2011 at 9:47 PM, John Dickinson m...@not.mn wrote:
What benefits does an openstack-satellite project bring? Other than all using
some openstack component, what do these projects have in common that
justifies grouping them? For example, I know of many open source projects
I am also interested in this.
On Thu, Apr 14, 2011 at 9:15 AM, Edward koko Konetzko
konet...@quixoticagony.com wrote:
On 04/14/2011 11:07 AM, Sandy Walsh wrote:
I've been getting a lot of questions about Zones lately.
How much interest is there for an informational session on Zones and, I
34 matches
Mail list logo
