Tangential question from the lurking writer: if I enable quotas and want
to modify them, do I use the nova quota* commands
as described here:
http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html ?
Thanks!
meg
On Wed, Apr 2, 2014 at 9:59 AM, kir.vondreth wrote:
> Hello,
>
> H
are solved.
meg
On Wed, Apr 2, 2014 at 11:45 PM, Mike Scherbakov
wrote:
> Sorry Meg,
> I can't really help as I'm overloaded these days.
>
> fuel-dev, any volunteer to help Meg with Sphinx?
>
> Thanks!
>
>
> On Tue, Apr 1, 2014 at 11:37 AM, Meg McRoberts wr
pate in the doc cleanup process.
>>
>>
>> 2014-04-03 10:45 GMT+04:00 Mike Scherbakov :
>>
>>> Sorry Meg,
>>> I can't really help as I'm overloaded these days.
>>>
>>> fuel-dev, any volunteer to help Meg with Sphinx?
>>>
>&g
x files for
> both cases. I'll try to refactor this later.
>
>
> 2014-04-03 12:15 GMT+04:00 Meg McRoberts :
>
> Thanks, Dmitry! I just fixed that -- let's see if Jenkins can build it
>> now.
>>
>> Can anyone explain why we need separate sourcing
Great info, Dmitriy! And yes, we need a straight-forward Installation
Guide for bare-metal that guides
the user through the basic, common steps; we also need a User Guide that is
simple and straightforward
for information about general maintenance/admin tasks after installation.
These guides can
Could someone please review
http://docs.mirantis.com/fuel/fuel-4.1/openstack-patch-quick-ref.html to
ensure that
it is still accurate for 5.0 then, especially since it sounds like this is
going to be the only way to apply patches. Feel
free to fix the docs or send comments to me and I'll be happy
A first draft of the Terminology Reference is available for review:
https://review.openstack.org/#/c/88662/
The blueprint is here:
https://blueprints.launchpad.net/fuel/+spec/term-reference-doc
I will be adding a lot more content -- you will notice that the current
doc has some terms that might
11:34 PM, Mike Scherbakov
wrote:
> Hi Meg,
> do we plan to land it in 5.0?
>
>
>
> On Tue, Apr 22, 2014 at 3:43 AM, Meg McRoberts wrote:
>
>>
>> A first draft of the Terminology Reference is available for review:
>>
>> https://review.opens
In an effort to create a "cleaner" Installation Guide, I have moved
the documentation about running Fuel on VirtualBox into a separate
document. I did a bit of editing and added a link to the cygwin page,
but the content is unchanged.
Making this a wonderful document is not a high priority for 5.
Hi, all,
I moved the OpenStack Patching Guide into a "chapter" in the Operations
Guide.
Other than modifying the heading levels, I made no changes from what was
there
in 4.1 (and I think 4.0).
Does anyone want to review?
https://review.openstack.org/#/c/90208/
Thanks much,
meg
--
Mailing list:
Please review https://review.openstack.org/#/c/90627/
I attempted a quick-fix on the general architecture information
to reflect that 5.0 no longer has the distinct multi-mode versus
multi-node with HA models.
Eventually, I would like this section to include discussions about
all the services --
The FAQ includes the following; should this be included in the introductory
material somewhere or should it be relegated to Marketing documentation
and removed from the technical documentation?
meg
1. **[Q]** Why did you decide to provide OpenStack packages through your own
repository?
**[
Please review https://review.openstack.org/#/c/90657/
This is a massive commit to move information from the FAQ
and User Guide to the Operations Guide. I did a bit of editing
along the way but the content is pretty much unchanged from
what was in the 4.1 docs.
For the sake of sanity, I'd like to
The
fuel-docs/frequently-asked-questions/0030-add-remove-nodes-without-downtime
file is marked as not ready to be included in the documentation. Does
anyone know the
history here? It would be a nice piece to include in the Operations Guide
but it needs a
bit of work.
Any thoughts?
meg
--
Mailin
Hi, all,
Here it is -- I know you've been looking forward to this... Time to update
the list of supported software for 5.0. I've made a few changes to the list
but I know I have missed some of it. So please review and correct:
https://review.openstack.org/#/c/90944/1
Thanks much,
meg
--
Maili
The User Guide in 5.0 will describe how to use Fuel to
deploy an OpenStack environment. The material that was
previously in the User Guide has been relocated to other
places in the doc set.
Please review https://review.openstack.org/#/c/92075/1,
looking only at the left column. Do I have all the
Hi, all. I need to take screen shots of Fuel 5.0. I have the following
URL:
http://fuelweb.vm.mirantis.net:8000/#clusters. I can get a few here, but
the screen where one chooses Sahara, Murano, and Ceilometer has no
place to check ones selections if one chooses nova-network -- it has a
note tha
Hi, all,
I'd love to hear opinions about this section of the docs:
http://docs.mirantis.com/fuel/master/install-guide.html#prerequisites
It seems like at least some of this is superfluous since we have the
Hardware Calculator, but some of it might be a bit interesting. Is it
out-of-date?
If it
nning" though. Also, I would add numbering
> like 1), 1.1) etc. It's hard to navigate otherwise
>
> ---
> Regards,
> Dmitriy
>
>
> On Wed, May 14, 2014 at 10:08 PM, Meg McRoberts
> wrote:
>
>> Hi, all,
>> I'd love to hear opinions about th
I have added items for the Fixed Issues and Known Issues in the 5.0 Release
Notes. Please review the content. Note that the Release Notes cannot be
built at this time but you should be able to review the content while I
figure out
the build problems.
https://review.openstack.org/#/c/92984/
If
The revamped User's Guide draft is finally available for review on gerrit:
https://review.openstack.org/#/c/92075/
This document covers "how to use Fuel to set up your OpenStack environment".
The general structure is one screen shot per section so we have room to add
information and hints. I wil
Does anyone have notes about "considerations" for choosing
between nova-network, neutron, and the two topologies each
supports?
Similarly, what can we tell people about choosing between CentOS
and Ubuntu for the host OS on the nodes?
I'm trying to do a quick save on the "Planning Guide" for 5.0.
A reminder that the Fixed and Known Issues sections of the Release
Notes are in serious need of technical review:
https://review.openstack.org/#/c/92984/
If you owned or fixed or cared about a particular LP, please check what
I said about it. All new issues are identified by LP number in the fil
I have the following note in the 5.0 Release Notes.
Do we know that the Ubuntu distro in our release
supports these CPUs?
Thanks much,
meg
CentOS does not support some newer CPUs
---
The CentOS does not support some recent CPUs
such as the latest Ultra Low Vol
At long last, we have a reasonable version of the 5.0 docs
staged and viewable:
http://docs.mirantis.com/openstack/fuel/fuel-5.0/index.html
I have a lot more work to do and we aren't going to get the
docs perfect for 5.1, but I think they are structured better
than they were and we are well posit
Hi, all. Does anyone have a sentence or two (or more) to add about MongoDB
in OpenStack 5.0?
This is the terminology article I have:
http://docs.mirantis.com/openstack/fuel/fuel-5.0/terminology.html#mongodb
It is just a bit weak, I'd say...
I would like to have at least enough information to te
o know bugs of
> Ceilometer+MySQL Web GUI part of Ceilometer part didn't work
> - In 5.x we use MongoDB as backend for Ceilometer - all should be working
> neatly now :)
>
> ---
> Regards,
> Dmitriy
>
>
> On Sat, May 24, 2014 at 8:23 AM, Meg McRoberts wrote:
>
>>
Hi, all,
I need a bit of "high-level" hardware planning advice. This is all I have
--
does anyone have something better sitting around. If not, I may be able
to improve this a bit but...
It would be nice to briefly mention how one determines whether to buy,
say, one super-powerful server versus
ww.mirantis.com/openstack-services/bom-calculator/ - "How it
> works" tab is super useful, even though will probably trigger even more
> questions
> 2) http://docs.openstack.org/ops/ - still reading through my paper copy
> from summit
>
> ---
> Regards,
> Dmitriy
&g
vs...@mirantis.com> wrote:
> *The roles-and-nodes screens do list MongoDB as a role that can be
>> assigned. *
>
>
> this is new to me ;( Feature owner to rescue!
>
> ---
> Regards,
> Dmitriy
>
>
> On Mon, May 26, 2014 at 12:22 AM, Meg McRoberts
> wrote:
&
04.4 ULV support.
>
>
> On Tue, May 27, 2014 at 6:36 AM, Mike Scherbakov > wrote:
>
>> I think Ubuntu is fine. Vladimir, can you confirm it?
>>
>> Thanks,
>>
>>
>> On Fri, May 23, 2014 at 10:29 PM, Meg McRoberts
>> wrote:
>>
>>
Hi, all,
I want to do some work on our docs about Storage. Here are the main
pieces we have now:
http://docs.mirantis.com/openstack/fuel/fuel-5.0/reference-architecture.html#storage-nodes
http://docs.mirantis.com/openstack/fuel/fuel-5.0/reference-architecture.html#storage-architecture
Also a fe
Does anyone know what this error message means?
./launch.sh
Checking for 'expect'... OK
If you run this script under Cygwin, you may have to add path to VirtualBox
directory to your PATH.
Usually it is enough to run "export PATH=$PATH:"/cygdrive/c/Program
Files/Oracle/VirtualBox"
Checking for "VB
Fuel 5.0 ISO in the virtualbox/iso directory. you
> should copy it there
>
> On Tue, Jun 17, 2014 at 1:47 PM, Meg McRoberts
> wrote:
> > Does anyone know what this error message means?
> >
> > ./launch.sh
> > Checking for 'expect'... OK
> >
Jesse and others make a very good point. The Settings screen has already
become a real mess
that needs to be split up and organized a bit. I'm told that the serious
restructuring should come
after we implement the plug-ins scheme (currently planned for 6.0). And
each section definitely
needs an
e over provisioned and
>>>>> > unreliable due to default Fuel setting (prod KVM clouds often use
>>>>> > super-soft overcommit setting, or no overcommit at all)
>>>>> > - finally - *user will have to MANUALLY specify and maintain
>>>&g
Remember the brohaha about Icehouse features not supported/deployed
by Fuel, etc? I drafted a pathetic bit of doc:
https://review.openstack.org/#/c/101332
The conversation has grown cold... I need some more information to get
this right -- can anyone help?
This is related to https://bugs.launc
And yes, that section about choosing Ceph, etc belongs in the Planning
Guide --
I'm working on it:
https://review.openstack.org/#/c/100051/
I've got more work to do on that piece but feel free to add comments with
additional
information you'd like.
meg
On Wed, Jun 25, 2014 at 8:45 AM, Miroslav
5.0.1 is our first Fuel release that allows customers to (a) upgrade from
the
previous release and (b) run Fuel to support environments using different
versions. At least, this is the hope and the promise in the 5.0 Release
Notes.
I need information about how to do this for the 5.0.1 docs -- who
I can't comment on the substance here but, if someone gets me the
information, we now have
an Operations Guide in fuel-docs and we could put the information there
rather than in a wiki
or white paper.
meg
On Tue, Jul 1, 2014 at 4:19 PM, Dmitriy Novakovskiy <
dnovakovs...@mirantis.com> wrote:
>
> do you need? Do you need some instruction how to run upgrade procedure?
>
> Also Vitaly Kramskikh is our UI developer, I think he can provide some
> screenshots.
>
>
> On Tue, Jul 1, 2014 at 3:35 AM, Meg McRoberts
> wrote:
>
>> 5.0.1 is our first Fuel release t
nts is tentatively expected in the 5.1 milestone and
> upgrading of the environment (e.g. from Icehouse to Juno) is tentatively
> expected in the 6.x milestones.
>
> Thanks,
> - David J. Easter
> Director of Product Management, Mirantis, Inc.
>
> http://openstacksv.com/
&
h this Fuel Master Node then).
>
>
> Aleksey Kasatkin
>
>
>
> On Thu, Jul 3, 2014 at 2:31 AM, Meg McRoberts
> wrote:
>
>> Thanks for the clarification, David. This means that the feature
>> description in the 5.0 Release Notes is wrong -- I'll work on it.
>&
New release avaialble: Icehouse on CentOS 6.5 (2014.1.1-5.0.1)
>
> It seems that upgrade algorithm will be the same in production.
>
>
>
> Aleksey Kasatkin
>
>
>
> On Fri, Jul 4, 2014 at 12:48 PM, Meg McRoberts
> wrote:
>
>> Thank for this, Aleksey. I
device:
> mount -r -t iso9660 /dev/sr0 /mnt/media # mount DVD
> mount -r /dev/sdb1 /mnt/media # mount USB device
>
>
> Thanks,
>
> - David J. Easter
> Director of Product Management, Mirantis, Inc.
>
>
> From: Meg McRoberts
> Date: Tuesday, Jul
install 5.0.1 directly rather than upgrading from 5.0? Will this
drop-down then have only the two 5.0.1 releases?
meg
On Tue, Jul 8, 2014 at 4:02 PM, David Easter wrote:
> +1
>
> Thanks,
>
> -Dave Easter
>
> From: Meg McRoberts
> Date: Tuesday, July 8, 2014 at 3:
I could certainly add this text to the docs -- we have this absolutely
hideous page in the docs:
http://docs.mirantis.com/openstack/fuel/master/user-guide.html#network-settings
and it would
be really nice to break it up and give an explanation. Although we do need
to do it for all four
topologies.
> we are going to implement advanced networking
>>> <https://blueprints.launchpad.net/fuel/+spec/advanced-networking> and
>>> there will be a set of predefined networks which can be renamed, new ones
>>> can be added, etc. So I think it is better to keep this stuf
Yes, the Fuel UI does need a usability review -- it's such a nice interface
with
just a few little rough spots.While you are at it, feel free to
critique the User's
Guide, which in a way is an extension of the Fuel UI:
http://docs.mirantis.com/openstack/fuel/master/user-guide.html#settings-tab
A reminder that the 5.0.1 Release Notes draft is available for
comments/corrections:
https://review.openstack.org/#/c/104369/
Developers, if you own a bug being reported for the first time in 5.0.1 or
fixed
in 5.0.1, please verify that it is covered appropriately. Support and
service
people, fe
this. I suggest to use bug on
>> LP and provide manual recovery procedure as a comment to the bug, and then
>> you can use direct link in release notes to the comment.
>>
>> Thanks,
>>
>>
>> On Mon, Jul 21, 2014 at 2:27 PM, Meg McRoberts
>> wrote:
>
ms from "not supported" IceHouse features.
>
> But official documentation
> <http://docs.openstack.org/openstack-ops/content/scaling.html#Availability_Zones_and_Host_Aggregates>
> looks
> outdated, because they still
> require "configuration changes to nova.conf&qu
We should check with our training people to see what they need. For
example, any
reasonable evaluation of MongoDB (used for Ceilometer) or Zabbix probably
requires
a lot more resources than people are going to have on their personal
machine, but it
would be nice if they could configure some sort o
Just to clarify, are the upgrade instructions for 5.1 to run upgrade.sh
twice
or are you making ./upgrade.sh run itself twice for one user command?
I just created https://bugs.launchpad.net/fuel/+bug/1360372 to cover the
5.1 upgrade instructions.
On Fri, Aug 22, 2014 at 6:44 AM, Evgeniy L wrote
, it will roughly double the time yes.
>>>
>>> On Fri, Aug 22, 2014 at 11:56 PM, David Easter
>>> wrote:
>>> > Also, what is the effect on the user experience? If the process is run
>>> > twice - even automatically - is this going to double the upgr
Do we have any sort of detailed description about what is in 5.0.2?
Or maybe what is in 5.1 that is not in 5.0.2?
Thanks much!
meg
--
Mailing list: https://launchpad.net/~fuel-dev
Post to : fuel-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~fuel-dev
More help : https://help.l
verts commit 27838
> Related-bug: #1341656
> --
>
> 32.
> Add openstack dependencies installation for 5.0.2
>
> Add explicit 5.0.2 packages installation for 5.0.2
> Fuel release
>
> Closes-bug: #1359705
> --
>
> 33.
> Add missing notify dep
gt; One would not.
> Upgrading master node to 5.1 also automatically upgrades 5.0.x components
> to 5.0.2
>
>
> On Thu, Sep 4, 2014 at 9:57 PM, Meg McRoberts
> wrote:
>
>> Thanks, Miroslav! A couple more questions:
>>
>> - What is the succinct explanation for why one
he action
>> of updating.
>>
>> Thanks,
>>
>> - David J. Easter
>> Director of Product Management, Mirantis, Inc.
>>
>> From: Miroslav Anashkin
>> Date: Thursday, September 4, 2014 at 9:35 PM
>> To: Meg McRoberts
>>
>> Cc:
I sketched out the doc for redeploying, adding, and removing nodes.
Please review and correct/add information.
https://review.openstack.org/#/c/110757/4
Thanks much!
meg
--
Mailing list: https://launchpad.net/~fuel-dev
Post to : fuel-dev@lists.launchpad.net
Unsubscribe : https://launchpad.ne
I'd like to capture this in the documentation. The networking doc really
needs a major rewrite
and that isn't going to happen for 5.1. But I see two possibilities:
- Add a section called "Logical network configuration options" -- maybe you
have a better title --
to the Planning Guide. Does an
Thanks for the heads-up -- I'm writing this up now.
The Create and Configure sections of the User Guide need some really
nit-picking reviews -- the basic information is pretty much there but it
lacks
depth and richness...
On Thu, Sep 11, 2014 at 1:18 PM, Aleksandr Shaposhnikov
wrote:
> Sergii,
cumentation, Meg, over a year ago :)
>
> On Fri, Sep 12, 2014 at 12:21 AM, Meg McRoberts
> wrote:
>
>> Thanks for the heads-up -- I'm writing this up now.
>>
>> The Create and Configure sections of the User Guide need some really
>> nit-picking reviews -- the
It looks like we need to update the documentation about Public and Floating
IPs:
http://docs.mirantis.com/openstack/fuel/master/reference-architecture.html#public-and-floating-ip-address-requirements
I think I should change, "Each deployed node requires one IP address from
the Public network"
to
Hi, all,
I don't know if this is interesting. I'm playing with the 9/10 ISO in
VirtualBox. I started Fuel a few days ago but didn't click "Deploy
Changes" until now.
I defined a Controller Node, a Compute/Cinder node, and a Zabbix
node. I've been getting messages that the Zabbix node was offlin
figuration of controllers, and they always
>> are allocated public IP addresses).
>>
>> On Fri, Sep 12, 2014 at 1:41 PM, Meg McRoberts
>> wrote:
>> > It looks like we need to update the documentation about Public and
>> Floating
>> > IPs:
>> >
nodes? Someone said
that a MongoDB node
is really a storage node. I'm not sure...
meg
On Mon, Sep 15, 2014 at 2:09 AM, Meg McRoberts
wrote:
> Thanks so much for clearing that up, Aleksey -- I did not understand that.
> I just modified the source -- I need to rework the example (which
s names we use to not confuse
> someone: cinder, ceph, mongo.
>
>
>
> Aleksey Kasatkin
>
>
> On Mon, Sep 15, 2014 at 12:35 PM, Meg McRoberts
> wrote:
>
>> About the example... I'm thinking that I should go back to the old
>> definition of the environment h
A reminder that the Release Notes need reviewing -- we have very
few comments and they must be completed by Wednesday.
Irina is working on the resolved and known issues:
https://review.openstack.org/#/c/117672/. We still have a lot of known
issues that don't include work-arounds
or many details a
I think I finally have a decent draft of the upgrade/update doc.
I pared the text down significantly in light of the pared down
functionality.
Thanks to all of you who provided comments to earlier drafts;
please review this:
https://review.openstack.org/#/c/116422/
--
Mailing list: https://launch
Please review the docs about "Logs and Messages"
https://review.openstack.org/#/c/122054
In particular, I could use some help with the descriptions of the logs in
https://review.openstack.org/#/c/122054
Thanks much!
meg
--
Mailing list: https://launchpad.net/~fuel-dev
Post to : fuel-dev@l
Just to keep everyone in the loop... The Release Notes commit
you've been looking at is now frozen so it can be merged.
The latest changes to the Release Notes are in:
https://review.openstack.org/#/c/123235.
Please continue to send comments. Today is absolutely the
last day for all doc change
I agree. One could argue that people want to do this and are going to try
so we may as well
share what we know about doing this, including the warnings.
I will work with Aleksandr to get the details. I will write this up in the
Operations Guide and include
a link from the Planning Guide section
Hi, all,
Thanks to those of you who have been reviewing the docs faithfully.
I need more reviews of two pieces:
Storage Planning: https://review.openstack.org/#/c/124547/
Hardware Reqs for Target nodes: https://review.openstack.org/#/c/123829/
A reminder that review comments are welcome whether
74 matches
Mail list logo
