What about using something like jclouds?
https://github.com/jclouds/jclouds/blob/master/apis/cloudstack/src/test/java/org/jclouds/cloudstack/compute/CloudStackExperimentLiveTest.java
On Sat, Dec 27, 2014 at 12:06 AM, Giri Prasad
wrote:
> Hi All,
> Could somebody inform about books/reading mate
Hi All,
Could somebody inform about books/reading material on how to write application
programs, using the cloudstack infra.
I am planning to do java and php applications using cs infra, on linux vm's.
Then later on, to do some .net programming on windows vm's.
Any reference on how to do the a
On storage nodes - yes definitively will do it.
One finall advice/opinion please...?
On compute nodes, since one 10G will be shared by both primary and
secondary traffic - would you separate that on 2 different VLANs and then
implement some QoS i.e. guarantie 8Gb/s for primary traffic vlan, or i.
Actually, I would highly consider nic bonding for storage network if possible.
-Original Message-
From: Andrija Panic [mailto:andrija.pa...@gmail.com]
Sent: Friday, December 26, 2014 4:42 PM
To: d...@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: RE: Physical network desig
Thanks Somesh, first option also seems most logical to me.
I guess you wouldn't consider doing nic bonding and then vlans with some
QoS based on vlans on switch level?
Thx again
Sent from Google Nexus 4
On Dec 26, 2014 9:48 PM, "Somesh Naidu" wrote:
> I generally prefer to keep the storage tra
I generally prefer to keep the storage traffic separate. Reason is that storage
performance (provision templates to primary, snapshots, copy templates, etc)
significantly impact end user experience. In addition, it also helps isolate
network issues when troubleshooting.
So I'd go for one of the
Hi folks,
I'm designing some stuff - and wondering which crime to commit - I have 2
posible scenarios in my head
I have folowing NICs available on compute nodes:
1 x 1G NIC
2 x 10G NIC
I was wondering which approach would be better, as I', thinking about 2
possible sollutions at the moment, maybe
On Wed, Dec 24, 2014 at 12:45 AM, Rohit Yadav
wrote:
> Hi Hollman,
>
> The SAML2 auth plugin will be available starting 4.5.0 (I think it should
> be released during Jan 2015). Due to the way we work, we can backport the
> feature to 4.3 (since no db related changes are needed for this feature)
>
