can source openrc to set the environment variables that
the CLI uses. Look at those to get the same for Horizon's login:
source openrc
set | grep OS_
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev
and currently work for Nebula Inc. remotely from my home
outside Kansas City, MO (the Royals with a winning season and the Chiefs
with a 3-0 record? Inconceivable!).
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev
written
back to it again.
I prefer the former, overwriting localrc every time but that is a
significant change in behaviour, even if it is consistent with what we do
to the other OpenStack config files (rewriting them every time).
dt
--
Dean Troyer
dtro...@gmail.com
the current semantics of localrc
edits being effective immediately.
I want to keep this as simple as possible...
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
'
localrc to a local.conf [[local:localrc]] section; otherwise no change is
necessary
- local.generated will include the 'DO NOT EDIT' warning as it will be
re-created as-required when stackrc sources it
Am I missing anything?
dt
--
Dean Troyer
dtro...@gmail.com
/ that
will morph into the doc page in devstack.org when we're done.
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
project
configs; these would not necessarily be user-modifiable.
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to be able to specify the destination config file and
section in addition to the attribute name and value.
Thoughts?
dt
[Prompted by review https://review.openstack.org/44266]
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack
in that endpoint (no
parsing-guessing here!) due to backward-compatibility for older deployments.
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
.
*https://github.com/pixelb/crudini* https://github.com/pixelb/crudini
So +1 to getting rid of those.
Ditto
When we added support for these to DevStack it was for exactly those
options Dan mentioned, and that is still the only place they are used...
dt
--
Dean Troyer
dtro...@gmail.com
appreciation for a recipe to
duplicate an existing Nova Network config in Neutron. We can debate if
that belongs in Grenade should it ever exist...
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
as-needed or performed up
front and passed in to the clients would be extremely useful.
dt
--
Dean Troyer
dtro...@gmail.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
that particular failure yet.
dt
--
Dean Troyer
dtro...@gmail.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman
and call it both done and API stable.
+1
dt
--
Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
multiple purposes. In my mind it is still first and foremost a
development tool and quick way to build an OpenStack implementation
for multiple other uses such as CI gating, Grenade, POC demos,
whatever.
Program proposal forthcoming...
dt
--
Dean Troyer
dtro...@gmail.com
DevStack plays multiple roles in the development process for OpenStack.
Official Title: DevStack
PTL: Dean Troyer dtro...@gmail.com
Mission Statement: To provide an installation of OpenStack from git
repository master, or specific branches, suitable for development and
operational testing
401 - 416 of 416 matches
Mail list logo
