Yeah, at first I was thinking both simultaneous calls would succeed and two
accounts would be created (this is what happens when two volumes with the
same name are created because the volume ID is what really matters).
However, with accounts, the first will succeed and the others fail, which
can b
That is fine. But how do we convey this information to the Mgmt Server ?
Without making any enhancements to MgmtSvr/Agent , is it possible to achieve
this?
-Pradeep
On Saturday, December 21, 2013 4:19 AM, Chiradeep Vittal
wrote:
On the KVM host you could parse the output of 'brctl show',
It gives me immense pleasure to inform that the vote to label this ASF
4.2.1 RC as the GA release has been passed with following stats:
+1 : 6 votes includes 3 bindings from Daan, Wei and Chip.
+/-0 : from Tomasz.
Some issues have been pointed out by Tomasz (5422,5332 & 3806) and Andrei
(issue
Yes that is the current behaviour. All hosts in a cluster should be owned by a
single MS. In case when agent load balancing is enabled (agent.lb is set to
true), this constraint no longer holds and the hosts in a cluster may get split
across multiple MS.
If you look at the 'host' table there is
What is the account creation logic on Solidfire SAN if you try to create the
same simultaneously? I am assuming there should be some unique constraint like
account name/id etc. Try to see if this can be utilised so that one of the
account creation call fails with appropriate error/exception.
-K
Great, thanks, everyone.
Although I can get around this particular issue without the "InLockTable"
this time, "InLockTable" is really useful to know as I can see it coming
into play with other actions I may need to take.
On Sun, Dec 22, 2013 at 7:04 PM, Nitin Mehta wrote:
> Mike - I think your
Marcus - I think its still a bug. Could you please file it on Jira ?
Migration from NFS sec. storage to Object store is due in 4.3 I believe.
Check
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Sec
ondary+Storage+to+Object+Store
Thanks,
-Nitin
On 21/12/13 10:39 PM, "Ma
Mike - I think your use case can be answered by Alex's wiki [1] - handling
locking section.
You can look for where all the methods provided in Generic Dao (that end
in "InLockTable") is referred to get a better idea.
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Data+
I think just catching/handling the exception here will give you exactly
what you want. It doesn't eliminate the race but it mitigates any negative
impacts. Maybe change your logic to first "get_account", then based on
results you can do the create or not
On Dec 22, 2013 5:25 PM, "Mike Tutkowski"
Yeah, if it were just a single management server, I could use
"synchronized", but since it's not I was curious how we handle this
situation.
Perhaps your recommendation in regards to using a database table is the way
to go here. Do you know of any code in CloudStack that performs this kind
of acti
As far as I'm aware, most of this sort of thing is managed by the state
machines on the resources themselves, combined with the transactional
database to move between states it keeps the management servers in sync.
I'm not sure the problem is specific to having multiple mgmt servers. You'd
have th
Hi,
I was wondering how we control access to shared resources that are being
utilized by different management servers at the same time.
For example:
When a user attaches a volume (that's based on the SolidFire plug-in) to a
VM, my plug-in looks at the CloudStack account that is requesting the
op
Hi,
Assuming we have a situation with multiple management servers and a compute
cluster with more than one host, will all of the hosts in the same cluster
be "owned" by a single management server or is this not necessarily the
case?
Thanks!
--
*Mike Tutkowski*
*Senior CloudStack Developer, Soli
Hi All,
On Jenkins server, I see agents are in dead state.
Reason is there is no space left on the device.
Can anyone who had permission on Jenkins can please resolve this issue.
Thanks
Rajesh Battala
Hi,
4.3 Documentation is getting ready to be reviewed. Please review sections
Working with Snapshots, Virtual Machine Snapshots, and Implementing
VMSnapshotStrategy.
The documentation is uploaded at
https://issues.apache.org/jira/browse/CLOUDSTACK-4945.
Regards
-Radhika
Hi,
4.3 Documentation is getting ready to be reviewed. Please review section
Creating Compute Offering, which inludes the changes for the Dynamic Compute
offering .
The documentation is uploaded at
https://issues.apache.org/jira/browse/CLOUDSTACK-5604
Regards
-Radhika
16 matches
Mail list logo
