No, I mean an instance snapshot ;-) Please see the attached screenshot
of the "launch instance" dialog. I filed a bug report for that:
https://bugs.launchpad.net/horizon/+bug/1608565
Regards,
Eugen
Zitat von Turbo Fredriksson :
On Aug 1, 2016, at 3:11 PM, Eugen Block wrote:
Project->Comp
On Aug 2, 2016, at 8:08 AM, Eugen Block wrote:
> No, I mean an instance snapshot ;-) Please see the attached screenshot of the
> "launch instance" dialog. I filed a bug report for that:
> https://bugs.launchpad.net/horizon/+bug/1608565
That also works for me just fine..
Although the "Select B
Looking at
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::FloatingIP
I see that one of the attributes ('exports'?) is:
port_id
ID of the port associated with this IP.
However, when trying to use that in an output:
outputs:
port:
value: {
On Aug 2, 2016, at 11:28 AM, Turbo Fredriksson wrote:
> outputs:
>port:
> value: { get_attr: [port, port_id] }
> description: The port ID
If I try to use (the more obvious)
value: { get_resource: port }
I get:
Value must be a string
which I assume is because it's empty (i.
Which guide are you using?
I don't see any domains in your glance-api.conf or
glance-registry.conf, an excerpt from Mitaka guide:
---cut here---
[keystone_authtoken]
...
auth_uri = http://controller:5000
auth_url = http://controller:35357
memcached_servers = controller:11211
auth_type = passwo
Hi,
I’m having a bit of fun try to use AD for identifying and authorising Users on
Openstack .
The idea is to use AD for read-only access to users/group definitions, but all
authorisation data to be stored in SQL.
What works: Users can be authenticated (LDAP bind works, verification of the
use
Sean,
I would like to help you, but I need more information
1. could you please explain what means your phrase:
"On the command line with ldapsearch, users and groups can be listed (so
the attributes configured should be ok?)"
2. please try to use curl to debug:
- uncomment "admin_token = ADMIN" i
Sean,
the problem may be in the following: in Mitaka release keystone requires
user to have a role in the domain it's getting authZ'ing in. We ran into
the problem when Horizon tried to authZ user in Default domain and got
the same error.
On 02.08.2016 16:25, sean.bo...@swisscom.com wrote:
Hey guys,
I'm facing a hard time here to configure OpenStack Federation...
So far, I can login into Horizon using my Windows AD credentials but, I
can not use command line interface, the `openstack` command, with Federated
users.
Here is the error:
---
ubuntu@controller-1:~$ source ~/tmartin
Hi,
So I logged in as admin/default, then switched to the ldap
domain(horizon/identity/domains/), added a role.
Next try to add a user to that role (/horizon/identity/users), but “Unable to
retrieve user list”.
In /var/log/user.log I see
LDAP bind: who=cn=bind-user,dc=example,dc=net
<14>Aug 2
1. For example, to list users:
ldapsearch -x -D cn='service-account,dc=example,dc=net'
'(&(objectClass=person)(cn=*))' -W
2. admin_token is not commented it has a hash value, so doing
curl -v -s -H "X-Auth-Token: " http://192.168.0.2:5000/v3/users
< HTTP/1.1 401 Unauthorized
in the keystone
Guys,
I trying to configure OpenStack Federation and, right after logging into
Horizon with a Federated user, the following error appear on Apache /
Keystone logs:
---
Unable to retrieve project list.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/openstack_auth/user
Please send the tenant ids of all six neutron ports.
>From admin:neutron port-show | grep tenant_id
Thanks,Farhad.
On Monday, August 1, 2016 7:44 AM, Artem Plakunov
wrote:
Thanks.
You said though that classifier must be unique within a tenant. I tried
creating chains in two diffe
Hi, all. Trying to figure out how to disable a compute node from
getting new VMs scheduled for it on my Liberty cloud. I did see the
"nova host-update --maintenance" command, but (as noted elsewhere) it
seems not to work for KVM-based VMs. Is there a way to accomplish what
I'm looking to do?
On 29 July 2016 at 12:59, Martinx - ジェームズ wrote:
> Quick question:
>
> Can I start testing Newton VLAN Aware VMs now (Beta 2)?
>
> Thanks,
> Thiago
>
>
If you're paying close attention the LinuxBridge version is almost
functional, and the OVS one is coming along. I'd advise to wait a tad
longer.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Installation_and_Configuration_Guide/Safely_Removing_Compute_Resources.html
*nova service-disable HOST nova-compute*
*Rahul Sharma*
*MS in Computer Science, 2016*
College of Computer and Information
nova service-disable $SHORTNAME nova-compute --reason
NO_MORE_SCHEDULING_HERE
will prevent new VMs from going on but doesn't do anything with existing.
On Tue, Aug 2, 2016 at 3:01 PM, Ken D'Ambrosio wrote:
> Hi, all. Trying to figure out how to disable a compute node from getting
> new VMs sch
On 8/2/2016 5:34 PM, David Medberry wrote:
nova service-disable $SHORTNAME nova-compute --reason
NO_MORE_SCHEDULING_HERE
will prevent new VMs from going on but doesn't do anything with existing.
On Tue, Aug 2, 2016 at 3:01 PM, Ken D'Ambrosio mailto:k...@jots.org>> wrote:
Hi, all. Trying t
18 matches
Mail list logo