In the “Clone the Devstack repository” step of the manual you posted, that will
grab the devstack master branch. To work with icehouse, you need to grab the
stable/icehouse branch of devstack.
From: Ali Nazemian alinazem...@gmail.commailto:alinazem...@gmail.com
Date: Friday, September 26, 2014
I'm not sure on question 1, but the behavior you're seeing for question 2 is
due to nova quota-update expecting the tenant ID and not the tenant name.
$ nova help quota-update
usage: nova quota-update [--user user-id] [--instances instances]
[--cores cores] [--ram
Varun,
A few things to look into to narrow down where the problem is:
- Can you ping the Ops-Controller hostname from the host you're running the
glance command from? If not, there may be a networking issue preventing
communication with the host.
- On the Ops-Controller host, run netstat
main "default" to
>cloud_admin, so I assume that I should be able to list domains,
>projects etc.
>Until now I simply used the default config files for identity, can
>anyone advise how to configure that file properly?
>
>Regards,
>Eugen
>
>
>Zitat von Br
1. Yes, you can create new users in the "labA" domain via Horizon. Log in as
admin under the default domain, go to the Domains dashboard, and click the "Set
Domain Context" button for the "labA" domain. Then when you go back to the
create user workflow, the "labA" domain will be automatically
ted |
>+--+--+---
>---+-+-+---+
>| 465e2e9e201948668289ceb013277a50 | 89c5dcc8793d4867bae22d50e51e16b3
>| | | default | False |
>+--+--
Build Date : Fr 17 Jun 2016 05:07:19 CEST
>Build Host : build33
>Relocations : (not relocatable)
>Vendor : obs://build.opensuse.org/Cloud:OpenStack
>URL : http://wiki.openstack.org/OpenStackDashboard
>Summary : OpenStack Dashboard (Horizon)
>
>
>Any idea what g
There's currently no built in automation for Horizon to pull the policy file,
so you'll have to update it yourself on the Horizon instances.
Thanks,
Brad
From: Michael Gale >
Date: Wednesday, March 23, 2016 at 2:31 PM
To:
Currently, I think you need to have at least Keystone and Nova in each region
for Horizon to work. This is a known limitation, and there's ongoing work to
remove the Nova requirement [0]. I don't know of anything that can be done from
the Horizon side to restrict regions, but you could try
Hi Sergey,
The policies in github are expected to be this way. For many environments,
Domains are used to separate users (including domain admins) from doing bad
things to each other. Restricting access to the list of all domains in the
cloud is just one aspect of this separation, so that a
There's not a way to configure Horizon to do what you want, so you'd have
to write custom code to do that.
Also, there are security considerations to do it. Note that the default v3
keystone policy[1] doesn't allow just any user to list all domains in the
cloud. The list of domains is potentially
Please see the info here on things to watch for in the setup and common
configuration issues:
https://www.symantec.com/connect/blogs/domain-support-horizon-here
Thanks,
Brad
On 10/12/16, 10:47 AM, "Mindaugas" wrote:
>Hello,
>
>After dashboard was installed (newton
At Symantec, we provide a simple signup button on the Horizon login page
for self registration. Our goal is to not only make it easy for the user
to register but to also set up some basic things to make it easy for them
to start using OpenStack services. We don't use federated Keystone, so
users
. I therefore see that our VO
roles code can work perfectly well with your LDAP authn code.
regards
David
On 20/01/2015 17:43, Brad Pokorny wrote:
At Symantec, we provide a simple signup button on the Horizon login page
for self registration. Our goal is to not only make it easy for the
user
Hi all,
When a user is logged into Horizon and the Keystone token expires, I'm seeing
that the user gets logged out, even though the web session hasn't expired.
After some searching around and finding [1], it looks like this is expected, as
the implementation of Session Extendable Tokens
The last info I've found on the ML about a cross-region view in Horizon is [1],
which mentions making asynchronous calls to the APIs. Has anyone done further
work on such a view?
If not, I think it would make sense to only show the view if Searchlight is
enabled. One of the Searchlight use
The last I heard, oauth is likely to be deprecated in Keystone [1].
If you're interested in having it stay around, please let the Keystone team
know. It would only make sense to add it to Horizon if it's going to stay.
[1] http://openstack.markmail.org/message/ihqbetack26g5gmg
Thanks,
Brad
Hi Brian,
Copying to the general list, as this is something I've wondered about, and
others probably are as well.
Please see below. I'm not an expert on this topic, but I've looked at it a
little bit.
On 4/7/16, 11:02 AM, "Tully, Brian" wrote:
>Hi there -
>
>I'm reaching
+1. I think Rob will provide good input for stable.
Thanks,
Brad
From: Timur Sufiev >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date:
+1 I like it!
From: Akira Yoshiyama
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Thursday, July 21, 2016 at 9:02 AM
To:
Sorry guys, I'm a little late responding to this topic.
>From a Horizon perspective, it would help if there were an API to discover
whether custom locations are off or on in a Glance v2 installation. We
could then expose it to the user only if it's enabled.
What we've done to prevent this from
21 matches
Mail list logo