Could you attach copies of your Keystone policy.json file and your Horizon
keystone_policy.json file?
I use the same file for both horizon and keystone, it's attached to
this email. Please note that I changed the cloud_admin rule to use the
user_id of my admin user because domain_id didn't w
Can't you boot an instance without cinder?
Don't know, can I??
Well, you should ;-) How do you try to boot your instance, from CLI or
Horizon? If it's Horizon, you would have to NOT klick the button
"Create a new volume --> Yes" ;-) If it's CLI it's sufficient to only
execute "nova boot
Traditional network device vendors have embrace openstack.
So H3C and Huawei in china have implemented the solution.
发件人: Ops Cloud [mailto:o...@19cloud.net]
发送时间: 2016年6月21日 9:12
收件人: openstack@lists.openstack.org
主题: [Openstack] Virtual networking by hardware
Hi
Rather than the soft SDN solut
Hi Turbo,
The first thing I want to know
- Which VM are you creating(i.e; which OS image are you taking)?
- What size are you using and all?
Secondly,
- Which flavor are you using for VM creation.?
On Tue, Jun 21, 2016 at 12:56 PM, Eugen Block wrote:
> Can't you boot an instance wi
On Jun 21, 2016, at 11:40 AM, Abhishek Shrivastava wrote:
> The first thing I want to know
>
> - Which VM are you creating(i.e; which OS image are you taking)?
I've tried both the CirrOS and Debian GNU/Linux Jessie images.
http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
Have you tried any other flavors?
For instance if you are creating a 1GB volume then you can go for flavor
m1.tiny flavor.
So try creating a VM having boot volume size 1GB and use flavor m1.tiny
and see if it works.
On Tue, Jun 21, 2016 at 4:36 PM, Turbo Fredriksson wrote:
> On Jun 21, 2016,
On Jun 21, 2016, at 12:19 PM, Abhishek Shrivastava wrote:
> Have you tried any other flavors?
No, I never saw the point. The resources I specified was well within
the flavors rules. And the error was "Block Device Mapping is Invalid"
I can not see how changing the flavor would change that.
--
S
If it was the flavor, you would get different errors, something like
"flavor disk too small" or "out of memory". Again, I recommend to
launch an instance on local disk to see if that is working, then fix
the iscsi issue to be able to create volumes at all, first empty
volumes, then from an
Hey,
Cisco has a ML2 plugin, old style that integrates with the Nexus 9K to
offer vxlan hardware support.
Michael
On Mon, Jun 20, 2016 at 7:22 PM Ops Cloud wrote:
> Hi
>
> Rather than the soft SDN solution in neutron, is there any networking
> solution which is driven by hardware?
> What I mea
Hi everyone,
I've installed the openstack mitaka with packstack on a two-node setup to
get some common knowledge for the openstack. I use tempest to verify the
openstack components, so as for now I've got a couple of errors I hope you
can help me with. I've attached my latest errors log with the e
Hi,
First of all, think dis question did no get answered:
-I'll try that thanx. How do you do that with the "openstack" command?
If not, the command is: openstack volume create --size (size in GB) --image
(image name or id) volume_name
Just for info the cinder command was not exact, it should b
Hi Paul,
do you use this on RHEL? If you do then the rdo repo is ok, if you are using it
on CentOS then the packages have changed.
My 2 cents.
Remo
> On Jun 21, 2016, at 07:17, Paul S. wrote:
>
> Hi everyone,
>
> I've installed the openstack mitaka with packstack on a two-node setup to ge
>do you use this on RHEL?
No, actually I was using that on the CentOS 7.2, and I saw that repo as a
legit one in a lot of openstack guides available on the Internet. So what
repo should I use instead of it, and what would be the difference that I
should know of?
On Tue, Jun 21, 2016 at 5:51 PM, Re
On RHEL:
$ sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm
$ sudo yum update -y
$ sudo yum install -y openstack-packstack
$ packstack --allinone
On CentOS:
$ sudo yum install -y centos-release-openstack-mitaka
$ sudo yum update -y
$ sudo yum install -y openstack-packstack
$ pac
Thanks, I will try that to see how different repo will affect the tempest
errors that I get!
On Tue, Jun 21, 2016 at 6:59 PM, Remo Mattei wrote:
>
>- On RHEL:
>
>$ sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm
>$ sudo yum update -y
>$ sudo yum install -y op
On 06/17/2016 08:03 AM, Mohan Kumar wrote:
Karun,
Please check q-svc (neutron) service is running or not ! Error
complaining that keystone url is not reachable to authenticate , IP
192.168.202.130 should be reachable and keystone service should be
active .
Maybe you can rerun devstack if
We implemented something here at Symantec that sounds very similar to what
you¹re both talking about. We have three levels of Admin - Cloud, Domain,
and Project. If you¹re interested in checking it out, we actually
presented on this topic in Austin.
The presentation : https://www.youtube.com/watch
When you said "I use the same file for both horizon and keystone", I'm
wondering if that means your Keystone policy file in Horizon is called
policy.json. By default, it will need to be called keystone_policy.json.
And if you installed everything with devstack, it will need to be in
/opt/stack/hori
Hey everyone!
It's time to pick a name for the P and Q releases.
If you have a name you'd like us to vote on, please add it here:
https://wiki.openstack.org/wiki/Release_Naming/P_Proposals
https://wiki.openstack.org/wiki/Release_Naming/Q_Proposals
The nominations will be open until 2016-06-28
=
Ironic node information including credentials exposed to unathenticated users
=
:Date: June 21, 2016
:CVE: CVE-2016-4985
Affects
~~~
- Iro
2016-6-22 4:50 Monty Taylor [mailto:mord...@inaugust.com] wrote:
> Hey everyone!
>
> It's time to pick a name for the P and Q releases.
>
> If you have a name you'd like us to vote on, please add it here:
>
> https://wiki.openstack.org/wiki/Release_Naming/P_Proposals
>
> https://wiki.openstack
21 matches
Mail list logo
