You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by chris <cd...@gmail.com> on 2014/06/25 07:36:10 UTC
trying to upload a bootable VHD
I'm trying to use the .NET SDK to upload a bootable VHD to eventually use
to deploy a VM. I assume the correct sequence is upload > create template >
deploy VM.
However, when I upload a volume, there seems to be no way to make that
volume bootable (it's has the type DATADISK). Using it to create a template
once it's uploaded does not work. An error is thrown stating that that
image cannot be used to create a template.
I've also tried registering a template, using a URL to the VHD file I want
to upload in the process. Unfortunately, nothing seems to happen when I try
that. Going through this process also makes me wonder what the difference
of createTemplate & registerTemplate are. I get "create", but there's no
way to register a created template. If "register" creates one, why bother
with "create"?
I feel like I'm missing something obvious when failing at this process :)
Re: CloudStack and vSphere 5.1
Posted by al...@northbaysolutions.net.
Totally agree with musayev
Ali
*** This Message Has Been Sent Using BlackBerry Internet Service from Mobilink ***
-----Original Message-----
From: ilya musayev <il...@gmail.com>
Date: Fri, 27 Jun 2014 10:53:16
To: <us...@cloudstack.apache.org>
Reply-To: users@cloudstack.apache.org
Subject: Re: CloudStack and vSphere 5.1
With 4.3, secondary storage can be on NFS, S3, Swift or SMB/CIFS.
We dont support VMFS as secondary storage for following reasons (my
opinion):
* The file system needs to be clustered and availble on all hosts within
a zone (not just cluster or pod) - what if you have KVM, XEN, HyperV or
LXC in the same zone that cant read VMFS?
* It needs to be accessible from general linux OS (System Storage VM)
* VMFS - is proprietary FS that can only be accessed by vSphere ESXi hosts
It makes it much more complex by using VMFS as secondary storage, but if
enough people ask for, perhaps it will change.
On 6/26/14, 3:05 PM, José Egas López wrote:
> Thanks ilya, I already installed CS 4.2, so I can't add secondary
> storage by VMFS in this version?
>
> So, do you mean in 4.3 this feature is available?
>
> *
> José
>
> *
>
> El 26/06/2014 16:54, ilya musayev escribió:
>> I'm using NFS and VMFS (can be SAN or Local).
>>
>> I'd suggest an update to 4.3 - when 4.3.0.1 comes out.
>>
>> If you can build from source, i'd recommend doing it against 4.3
>> branch - this way you dont have to wait for 4.3.0.1 release.
>>
>> With newer release there are many more features and bug fixes when it
>> comes to vmware integration.
>>
>> Regards
>> ilya
>>
>> On 6/26/14, 12:35 PM, Erik Weber wrote:
>>> I believe you can use Vmfs as well.
>>>
>>> Erik
>>> 26. juni 2014 19:12 skrev "José Egas López" <jo...@farmaenlace.com>
>>> følgende:
>>>
>>>> Hi, I have one question, I'm trying to implement CS 4.2 with
>>>> vSphere 5.1,
>>>> which way can I use to configure Primary and Secondary Storages
>>>> without
>>>> using NFS?
>>>> Thanks to all for the help!
>>>>
>>>> *
>>>>
>>>> José
>>>>
>>>> *
>>>>
>>>>
>>>> ####################################################
>>>> FARMAENLACE ha procesado su mensaje y esta limpio
>>>> No imprima este mail a menos que sea necesario
>>>>
>>>>
>>
>>
>> ####################################################
>> FARMAENLACE ha procesado su mensaje y esta limpio
>> No imprima este mail a menos que sea necesario
>>
>
>
> ####################################################
> FARMAENLACE ha procesado su mensaje y esta limpio
> No imprima este mail a menos que sea necesario
>
>
Re: CloudStack and vSphere 5.1
Posted by ilya musayev <il...@gmail.com>.
With 4.3, secondary storage can be on NFS, S3, Swift or SMB/CIFS.
We dont support VMFS as secondary storage for following reasons (my
opinion):
* The file system needs to be clustered and availble on all hosts within
a zone (not just cluster or pod) - what if you have KVM, XEN, HyperV or
LXC in the same zone that cant read VMFS?
* It needs to be accessible from general linux OS (System Storage VM)
* VMFS - is proprietary FS that can only be accessed by vSphere ESXi hosts
It makes it much more complex by using VMFS as secondary storage, but if
enough people ask for, perhaps it will change.
On 6/26/14, 3:05 PM, José Egas López wrote:
> Thanks ilya, I already installed CS 4.2, so I can't add secondary
> storage by VMFS in this version?
>
> So, do you mean in 4.3 this feature is available?
>
> *
> José
>
> *
>
> El 26/06/2014 16:54, ilya musayev escribió:
>> I'm using NFS and VMFS (can be SAN or Local).
>>
>> I'd suggest an update to 4.3 - when 4.3.0.1 comes out.
>>
>> If you can build from source, i'd recommend doing it against 4.3
>> branch - this way you dont have to wait for 4.3.0.1 release.
>>
>> With newer release there are many more features and bug fixes when it
>> comes to vmware integration.
>>
>> Regards
>> ilya
>>
>> On 6/26/14, 12:35 PM, Erik Weber wrote:
>>> I believe you can use Vmfs as well.
>>>
>>> Erik
>>> 26. juni 2014 19:12 skrev "José Egas López" <jo...@farmaenlace.com>
>>> følgende:
>>>
>>>> Hi, I have one question, I'm trying to implement CS 4.2 with
>>>> vSphere 5.1,
>>>> which way can I use to configure Primary and Secondary Storages
>>>> without
>>>> using NFS?
>>>> Thanks to all for the help!
>>>>
>>>> *
>>>>
>>>> José
>>>>
>>>> *
>>>>
>>>>
>>>> ####################################################
>>>> FARMAENLACE ha procesado su mensaje y esta limpio
>>>> No imprima este mail a menos que sea necesario
>>>>
>>>>
>>
>>
>> ####################################################
>> FARMAENLACE ha procesado su mensaje y esta limpio
>> No imprima este mail a menos que sea necesario
>>
>
>
> ####################################################
> FARMAENLACE ha procesado su mensaje y esta limpio
> No imprima este mail a menos que sea necesario
>
>
Re: CloudStack and vSphere 5.1
Posted by José Egas López <jo...@farmaenlace.com>.
Thanks ilya, I already installed CS 4.2, so I can't add secondary
storage by VMFS in this version?
So, do you mean in 4.3 this feature is available?
*
José
*
El 26/06/2014 16:54, ilya musayev escribió:
> I'm using NFS and VMFS (can be SAN or Local).
>
> I'd suggest an update to 4.3 - when 4.3.0.1 comes out.
>
> If you can build from source, i'd recommend doing it against 4.3
> branch - this way you dont have to wait for 4.3.0.1 release.
>
> With newer release there are many more features and bug fixes when it
> comes to vmware integration.
>
> Regards
> ilya
>
> On 6/26/14, 12:35 PM, Erik Weber wrote:
>> I believe you can use Vmfs as well.
>>
>> Erik
>> 26. juni 2014 19:12 skrev "José Egas López" <jo...@farmaenlace.com>
>> følgende:
>>
>>> Hi, I have one question, I'm trying to implement CS 4.2 with vSphere
>>> 5.1,
>>> which way can I use to configure Primary and Secondary Storages without
>>> using NFS?
>>> Thanks to all for the help!
>>>
>>> *
>>>
>>> José
>>>
>>> *
>>>
>>>
>>> ####################################################
>>> FARMAENLACE ha procesado su mensaje y esta limpio
>>> No imprima este mail a menos que sea necesario
>>>
>>>
>
>
> ####################################################
> FARMAENLACE ha procesado su mensaje y esta limpio
> No imprima este mail a menos que sea necesario
>
####################################################
FARMAENLACE ha procesado su mensaje y esta limpio
No imprima este mail a menos que sea necesario
Re: CloudStack and vSphere 5.1
Posted by ilya musayev <il...@gmail.com>.
I'm using NFS and VMFS (can be SAN or Local).
I'd suggest an update to 4.3 - when 4.3.0.1 comes out.
If you can build from source, i'd recommend doing it against 4.3 branch
- this way you dont have to wait for 4.3.0.1 release.
With newer release there are many more features and bug fixes when it
comes to vmware integration.
Regards
ilya
On 6/26/14, 12:35 PM, Erik Weber wrote:
> I believe you can use Vmfs as well.
>
> Erik
> 26. juni 2014 19:12 skrev "José Egas López" <jo...@farmaenlace.com>
> følgende:
>
>> Hi, I have one question, I'm trying to implement CS 4.2 with vSphere 5.1,
>> which way can I use to configure Primary and Secondary Storages without
>> using NFS?
>> Thanks to all for the help!
>>
>> *
>>
>> José
>>
>> *
>>
>>
>> ####################################################
>> FARMAENLACE ha procesado su mensaje y esta limpio
>> No imprima este mail a menos que sea necesario
>>
>>
Re: CloudStack and vSphere 5.1
Posted by Erik Weber <te...@gmail.com>.
I believe you can use Vmfs as well.
Erik
26. juni 2014 19:12 skrev "José Egas López" <jo...@farmaenlace.com>
følgende:
> Hi, I have one question, I'm trying to implement CS 4.2 with vSphere 5.1,
> which way can I use to configure Primary and Secondary Storages without
> using NFS?
> Thanks to all for the help!
>
> *
>
> José
>
> *
>
>
> ####################################################
> FARMAENLACE ha procesado su mensaje y esta limpio
> No imprima este mail a menos que sea necesario
>
>
Re: CloudStack and vSphere 5.1
Posted by ilya musayev <il...@gmail.com>.
Secondary storage at this point in time must reside on NFS. If its POC
setup, you can run NFS on the same server as your CloudStack Management
Server.
On 6/26/14, 10:08 AM, José Egas López wrote:
> Hi, I have one question, I'm trying to implement CS 4.2 with vSphere
> 5.1, which way can I use to configure Primary and Secondary Storages
> without using NFS?
> Thanks to all for the help!
>
> *
>
> José
>
> *
>
>
> ####################################################
> FARMAENLACE ha procesado su mensaje y esta limpio
> No imprima este mail a menos que sea necesario
>
>
CloudStack and vSphere 5.1
Posted by José Egas López <jo...@farmaenlace.com>.
Hi, I have one question, I'm trying to implement CS 4.2 with vSphere
5.1, which way can I use to configure Primary and Secondary Storages
without using NFS?
Thanks to all for the help!
*
José
*
####################################################
FARMAENLACE ha procesado su mensaje y esta limpio
No imprima este mail a menos que sea necesario
Re: trying to upload a bootable VHD
Posted by Nitin Mehta <Ni...@citrix.com>.
Chris - Please use the wiki [1] in case you see any issues registering
your template. That¹s the one you should use here.
[1] -
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Sec
ondary+storage+troubleshooting
On 25/06/14 5:16 AM, "chris" <cd...@gmail.com> wrote:
>Thanks.
>
>My attempt to register a template failed. It sounds like that's the
>command
>I want though. I'll go back and make sure I didn't do something wrong.
>
>I thought the dev@ address was for development of CloudStack itself?
>
>
>On Wed, Jun 25, 2014 at 12:54 AM, ilya musayev
><ilya.mailing.lists@gmail.com
>> wrote:
>
>> Chris,
>>
>> If you intend to boot from this VHD, it should be set as ROOT type.
>>
>> If you add a template through cloudstack UI or api - registerTemplate,
>>it
>> is set as type ROOT.
>>
>> If you use createTemplate, it will create a template from ROOT disk of
>> existing VMs ROOT disk.
>>
>> If you are using "upload volume", then its going to be a DATA disk.
>>
>> Try posting on dev@cloudstack.apache.org for better answer.
>>
>> Regards
>> ilya
>>
>>
>>
>>
>>
>> On 6/24/14, 10:36 PM, chris wrote:
>>
>>> I'm trying to use the .NET SDK to upload a bootable VHD to eventually
>>>use
>>> to deploy a VM. I assume the correct sequence is upload > create
>>>template
>>> >
>>> deploy VM.
>>>
>>> However, when I upload a volume, there seems to be no way to make that
>>> volume bootable (it's has the type DATADISK). Using it to create a
>>> template
>>> once it's uploaded does not work. An error is thrown stating that that
>>> image cannot be used to create a template.
>>>
>>> I've also tried registering a template, using a URL to the VHD file I
>>>want
>>> to upload in the process. Unfortunately, nothing seems to happen when I
>>> try
>>> that. Going through this process also makes me wonder what the
>>>difference
>>> of createTemplate & registerTemplate are. I get "create", but there's
>>>no
>>> way to register a created template. If "register" creates one, why
>>>bother
>>> with "create"?
>>>
>>> I feel like I'm missing something obvious when failing at this process
>>>:)
>>>
>>>
>>
Re: trying to upload a bootable VHD
Posted by chris <cd...@gmail.com>.
Thanks.
My attempt to register a template failed. It sounds like that's the command
I want though. I'll go back and make sure I didn't do something wrong.
I thought the dev@ address was for development of CloudStack itself?
On Wed, Jun 25, 2014 at 12:54 AM, ilya musayev <ilya.mailing.lists@gmail.com
> wrote:
> Chris,
>
> If you intend to boot from this VHD, it should be set as ROOT type.
>
> If you add a template through cloudstack UI or api - registerTemplate, it
> is set as type ROOT.
>
> If you use createTemplate, it will create a template from ROOT disk of
> existing VMs ROOT disk.
>
> If you are using "upload volume", then its going to be a DATA disk.
>
> Try posting on dev@cloudstack.apache.org for better answer.
>
> Regards
> ilya
>
>
>
>
>
> On 6/24/14, 10:36 PM, chris wrote:
>
>> I'm trying to use the .NET SDK to upload a bootable VHD to eventually use
>> to deploy a VM. I assume the correct sequence is upload > create template
>> >
>> deploy VM.
>>
>> However, when I upload a volume, there seems to be no way to make that
>> volume bootable (it's has the type DATADISK). Using it to create a
>> template
>> once it's uploaded does not work. An error is thrown stating that that
>> image cannot be used to create a template.
>>
>> I've also tried registering a template, using a URL to the VHD file I want
>> to upload in the process. Unfortunately, nothing seems to happen when I
>> try
>> that. Going through this process also makes me wonder what the difference
>> of createTemplate & registerTemplate are. I get "create", but there's no
>> way to register a created template. If "register" creates one, why bother
>> with "create"?
>>
>> I feel like I'm missing something obvious when failing at this process :)
>>
>>
>
Re: trying to upload a bootable VHD
Posted by ilya musayev <il...@gmail.com>.
Chris,
If you intend to boot from this VHD, it should be set as ROOT type.
If you add a template through cloudstack UI or api - registerTemplate,
it is set as type ROOT.
If you use createTemplate, it will create a template from ROOT disk of
existing VMs ROOT disk.
If you are using "upload volume", then its going to be a DATA disk.
Try posting on dev@cloudstack.apache.org for better answer.
Regards
ilya
On 6/24/14, 10:36 PM, chris wrote:
> I'm trying to use the .NET SDK to upload a bootable VHD to eventually use
> to deploy a VM. I assume the correct sequence is upload > create template >
> deploy VM.
>
> However, when I upload a volume, there seems to be no way to make that
> volume bootable (it's has the type DATADISK). Using it to create a template
> once it's uploaded does not work. An error is thrown stating that that
> image cannot be used to create a template.
>
> I've also tried registering a template, using a URL to the VHD file I want
> to upload in the process. Unfortunately, nothing seems to happen when I try
> that. Going through this process also makes me wonder what the difference
> of createTemplate & registerTemplate are. I get "create", but there's no
> way to register a created template. If "register" creates one, why bother
> with "create"?
>
> I feel like I'm missing something obvious when failing at this process :)
>