Re: storage affinity groups

[Yiping Zhang]

Yes, we are currently considering creating multiple clusters.  The downside of 
this approach is we need many more hosts.

Yiping

On 9/9/16, 4:05 PM, "Simon Weller"  wrote:

Why not just use different primary storage per cluster. You then can 
control your storage failure domains on a cluster basis.

Simon Weller/ENA
(615) 312-6068

-Original Message-
From: Will Stevens [wstev...@cloudops.com]
Received: Friday, 09 Sep 2016, 5:46PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: Re: storage affinity groups

I have not really thought through this use case, but off the top of my
head, you MAY be able to do something like use host anti-affinity and then
use different primary storage per host affinity.  I know this is not the
ideal solution, but it will limit the primary storage failure domain to a
set of affinity hosts.  This pushes the responsibility of HA to the
application deployer, which I think you are expecting to the be case
anyway.  You still have a single point of failure with the load balancers
unless you implement GSLB.

This will likely complicate your capacity management, but it may be a short
term solution for your problem until a better solution is developed.

If I think of other potential solutions I will post them, but that is what
I have for right now.

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Sep 9, 2016 at 3:44 PM, Yiping Zhang  wrote:

> Will described my use case perfectly.
>
> Ideally, the underlying storage technology used for the cloud should
> provide the reliability required.  But not every company has the money for
> the best storage technology on the market. So the next best thing is to
> provide some fault tolerance redundancy through the app and at the same
> time make it easy to use for end users and administrators alike.
>
> Regards,
>
> Yiping
>
> On 9/9/16, 11:49 AM, "Tutkowski, Mike"  wrote:
>
> Yep, based on the recent e-mail Yiping sent, I would agree, Will.
>
> At the time being, you have two options: 1) storage tagging 2)
> fault-tolerant primary storage like a SAN.
> 
> From: williamstev...@gmail.com  on behalf
> of Will Stevens 
> Sent: Friday, September 9, 2016 12:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: storage affinity groups
>
> My understanding is that he wants to do anti-affinity across primary
> storage endpoints.  So if he has two web servers, it would ensure that
> one
> of his web servers is on Primary1 and the other is on Primary2.  This
> means
> that if he loses a primary storage for some reason, he only loses one
> of
> his load balanced web servers.
>
> Does that sound about right?
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Sep 9, 2016 at 2:40 PM, Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> wrote:
>
> > Hi Yiping,
> >
> > Reading your most recent e-mail, it seems like you are looking for a
> > feature that does more than simply makes sure virtual disks are
> roughly
> > allocated equally across the primary storages of a given cluster.
> >
> > At first, that is what I imagined your request to be.
> >
> > From this e-mail, though, it looks like this is something you'd like
> users
> > to be able to personally choose (ex. a user might want virtual disk
> 1 on
> > different storage than virtual disk 2).
> >
> > Is that a fair representation of your request?
> >
> > If so, I believe storage tagging (as was mentioned by Marty) is the
> only
> > way to do that at present. It does, as you indicated, lead to a
> > proliferation of offerings, however.
> >
> > As for how I personally solve this issue: I do not run a cloud. I
> work for
> > a storage vendor. In our situation, the clustered SAN that we
> develop is
> > highly fault tolerant. If the SAN is offline, then it probably means
> your
> > entire datacenter is offline (ex. power loss of some sort).
> >
> > Talk to you later,
> > Mike
> > 
> > From: Yiping Zhang 
>  

Re: System VM's are getting stuck in starting mode

[Tutkowski, Mike]

Is your issue similar to this one?

https://issues.apache.org/jira/browse/CLOUDSTACK-9144

From: ned dogg 
Sent: Saturday, September 10, 2016 1:24 PM
To: dev@cloudstack.apache.org
Subject: System VM's are getting stuck in starting mode

Hi Everybody,

I'm a newbie on cloudstack. I started playing with this technology. For
that I install both the management -server and the agent. I was able to
install and start them properly but I unable to create any instance. When I
click on instance the menu then I  click on add instance and next, I have
no templates that is presented to me. Thus I stuck at this level. I don't
know what to do.

I think that this issue is because my System VM get stuck an the starting
mode. After some googling, I discovered that this is a know issue
https://issues.apache.org/jira/browse/CLOUDSTACK-7936. But this issue is
for cloudstack 4.4.1 but I'm using cloudstack 4.6. I was asking myself if
this issue is also common on cloudstack 4.6?

Please any help will be welcoming.
Thanks.

[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1660
  
@serg38 I will be going through other PRs tomorrow that are due for merge.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper a...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1660


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1660
  
@jburwell Thanks a lot. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1660
  
@rafaelweingartner @serg38 is correct.  Any committer may merge a PR so 
long as the following conditions are met:

   * At least 1 code review LGTM
   * At least 1 test LGTM
   * No -1s

I am merging this PR now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1660
  
@rafaelweingartner . Thanks. I believe per current process  any committer 
can merge PRs as  per below. We have so many PRs in merge ready state
 
Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1642
  
@mike-tukowski any committer may merge a PR with at least one code 
review LGTM, at least one test LGTM, and no -1s.  For this PR, I don't see a 
test LGTM with test results.  Until it has at least one test LGTM, it is *not* 
ready to merge.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

RE: System VM's are getting stuck in starting mode

[Simon Weller]

Hi,

Can you tell us more about your environment?

What hypervisor are you using? Is this a basic or advanced zone?



Simon Weller/ENA
(615) 312-6068

-Original Message-
From: ned dogg [neddog...@gmail.com]
Received: Saturday, 10 Sep 2016, 2:24PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: System VM's are getting stuck in starting mode

Hi Everybody,

I'm a newbie on cloudstack. I started playing with this technology. For
that I install both the management -server and the agent. I was able to
install and start them properly but I unable to create any instance. When I
click on instance the menu then I  click on add instance and next, I have
no templates that is presented to me. Thus I stuck at this level. I don't
know what to do.

I think that this issue is because my System VM get stuck an the starting
mode. After some googling, I discovered that this is a know issue
https://issues.apache.org/jira/browse/CLOUDSTACK-7936. But this issue is
for cloudstack 4.4.1 but I'm using cloudstack 4.6. I was asking myself if
this issue is also common on cloudstack 4.6?

Please any help will be welcoming.
Thanks.

System VM's are getting stuck in starting mode

[ned dogg]

Hi Everybody,

I'm a newbie on cloudstack. I started playing with this technology. For
that I install both the management -server and the agent. I was able to
install and start them properly but I unable to create any instance. When I
click on instance the menu then I  click on add instance and next, I have
no templates that is presented to me. Thus I stuck at this level. I don't
know what to do.

I think that this issue is because my System VM get stuck an the starting
mode. After some googling, I discovered that this is a know issue
https://issues.apache.org/jira/browse/CLOUDSTACK-7936. But this issue is
for cloudstack 4.4.1 but I'm using cloudstack 4.6. I was asking myself if
this issue is also common on cloudstack 4.6?

Please any help will be welcoming.
Thanks.

[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1660
  
@serg38 I do not know how it is working right now this process; but, I 
recall seeing an email saying that only RMs would be allowed to merge now. I 
might be mistaken, I had lost track of that thread, but just in case that is 
why I am not going forward right now and merging this PR. The same applies for 
your other PRs. Let’s see what others have to add on this here.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---