Re: Instance with a larger disk size then Template

[Mohd Zainal Abidin]

We have this issue long time ago. We manually resize root when VM's still
running. After resize and reboot the size show correct.

On Aug 4, 2017 6:25 AM, "ilya"  wrote:

> Just a thought - as i do this very frequently.
>
> If you are using LVM on your ROOT partition - you dont need to power it
> on via Live CD.
>
> It can all be done online while the system running.
>
>
>
>
> On 8/3/17 6:40 AM, Imran Ahmed wrote:
> > Hi Erik,
> >
> > Thanks for suggestion, I tried this too and was successful till
> lvextending the logical volume. However at the stage of running resize2fs
> it produced errors like : Bad super block..."  so I ended up installing
> from an ISO and partitioning without LVM this time so that I could use this
> template to resize in future.
> >
> > Cheers,
> >
> > Imran
> >
> > -Original Message-
> > From: Erik Weber [mailto:terbol...@gmail.com]
> > Sent: Thursday, August 03, 2017 3:56 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Instance with a larger disk size then Template
> >
> > A faster approach than those mentioned is to create a new partition on
> > the unused disk space, and add it to the volume group, then use
> > lvextend and resizing the fs.
> >
> > On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed  wrote:
> >> Hi All,
> >>
> >> I am creating an instance with a 300GB disk from a CentOS 7 template
> that
> >> has 5GB disk (LVM Based).
> >> The issue is that the root LVM partition inside the new VM instance
> still
> >> shows 5GB .
> >>
> >> The device size  (/dev/vda) however shows 300GB.  The question is what
> is
> >> the best strategy to resize the root LVM partition so that I could use
> all
> >> 300G.
> >>
> >> Kind regards,
> >>
> >> Imran
> >>
> >
>

Re: Instance with a larger disk size then Template

[ilya]

Just a thought - as i do this very frequently.

If you are using LVM on your ROOT partition - you dont need to power it
on via Live CD.

It can all be done online while the system running.




On 8/3/17 6:40 AM, Imran Ahmed wrote:
> Hi Erik,
> 
> Thanks for suggestion, I tried this too and was successful till lvextending 
> the logical volume. However at the stage of running resize2fs  it produced 
> errors like : Bad super block..."  so I ended up installing from an ISO and 
> partitioning without LVM this time so that I could use this template to 
> resize in future.
> 
> Cheers,
> 
> Imran 
> 
> -Original Message-
> From: Erik Weber [mailto:terbol...@gmail.com] 
> Sent: Thursday, August 03, 2017 3:56 PM
> To: users@cloudstack.apache.org
> Subject: Re: Instance with a larger disk size then Template
> 
> A faster approach than those mentioned is to create a new partition on
> the unused disk space, and add it to the volume group, then use
> lvextend and resizing the fs.
> 
> On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed  wrote:
>> Hi All,
>>
>> I am creating an instance with a 300GB disk from a CentOS 7 template that
>> has 5GB disk (LVM Based).
>> The issue is that the root LVM partition inside the new VM instance  still
>> shows 5GB .
>>
>> The device size  (/dev/vda) however shows 300GB.  The question is what is
>> the best strategy to resize the root LVM partition so that I could use all
>> 300G.
>>
>> Kind regards,
>>
>> Imran
>>
> 

Re: AW: Instance with a larger disk size then Template

[ilya]

Great feedback - did not know cloud-init supported this.



On 8/3/17 3:17 AM, S. Brüseke - proIO GmbH wrote:
> Hi Imran,
> 
> you are talking about 3 different levels here to reach your goal of resizing 
> a volume. First level is the volume itself. This is what you can do within 
> CS. After that you need to extend the partition and then you need to expand 
> the filesystem. The last to levels you need to do within the os of the server.
> 
> What we do is using cloud-init within our template to automate this. But our 
> templates do not use LVM. Our templates are checking at boot if the root 
> volume has been extended and expanding the partition and the filesystem.
> 
> If you want to know more about it, I can give you more details.
> 
> Mit freundlichen Grüßen / With kind regards,
> 
> Swen Brüseke
> 
> -Ursprüngliche Nachricht-
> Von: Imran Ahmed [mailto:im...@eaxiom.net] 
> Gesendet: Donnerstag, 3. August 2017 12:00
> An: users@cloudstack.apache.org
> Betreff: Instance with a larger disk size then Template
> 
> Hi All,
> 
> I am creating an instance with a 300GB disk from a CentOS 7 template that has 
> 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance  still 
> shows 5GB .  
> 
> The device size  (/dev/vda) however shows 300GB.  The question is what is the 
> best strategy to resize the root LVM partition so that I could use all 300G.
> 
> Kind regards,
> 
> Imran 
> 
> 
> 
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
> 
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. 
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben, 
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet. 
> 
> This e-mail may contain confidential and/or privileged information. 
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify 
> the sender immediately and destroy this e-mail.  
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden. 
> 
> 

Re: Some things I found out installing on Centos 7

[ilya]

Eric

Its a good feedback for us as community to focus on cleaning up
documentation. We are adding many features - and we need to make sure
they are properly reflected.


Also - way back when - some of the documentation was written by
technical writers sponsored by Citrix. I can only assume technical
writters did not understand what they were writting - because myself
being a cloudstack user for 5 years - i could not understand the meaning
of some sentences.

However what i failed to do - is raise an issue and help rewrite it.

Thanks for taking time to write this.

Regards,
ilya

PS:

I have mixed feelings with VMware implementation. I've been using it
since 2005. Perhaps for small to mid range setups - it will do well.

My experience with going above several hundred hypervisors was not
great. I wont go into details as to what happened - other than to say -
it has great number of challenges of its own (just like any other
solution). But i learned that KVM had less feature - but was also far
less complex and stable - and cloudstack helped bridge the gap of not
have vCenter.



On 8/2/17 1:12 AM, Eric Green wrote:
> First, about me -- I've been administering Linux systems since 1995. No, 
> that's not a typo -- that's 22 years. I've also worked for a firewall 
> manufacturer in the past, I designed the layer 2 VLAN support for a firewall 
> vendor, so I know VLAN's and such. I run a fairly complex production network 
> with multiple VLAN's, multiple networks, etc. already, and speak fluent Cisco 
> CLI. In short, I'm not an amateur at this networking stuff, but figuring out 
> how Cloudstack wanted my CentOS 7 networking to be configured, and doing all 
> the gymnastics to make it happen, consumed nearly a week because the 
> documentation simply isn't up to date, thorough, or accurate, at least for 
> Centos 7. 
> 
> So anyhow, my configuration:
> 
> Cloudstack 4.9.2.0 from the RPM repository at cloudstack.apt-get.eu
> 
> Centos 7 servers with:
> 
> 2 10gbit Ethernet ports -> bond0 
> 
> A handful of VLANS:
> 
> 100 -- from my top of rack switch is sent to my core backbone switch layer 3 
> routed to my local network as 10.100.x.x and thru the NAT border firewall and 
> router to the Internet. Management.
> 101 -- same but for 10.101.x.x  -- public.
> 102 -- same but for 10.102.x.x  -- guest public (see below).
> 192 -- A video surveillance camera network that is not routed to anywhere, 
> via a drop from the core video surveillance POE switch to an access mode port 
> on my top of rack switch. Not routed.
> 200 -- 10 gig drop over to my production racks to my storage network there 
> for accessing legacy storage. Not routed. (Legacy storage is not used for 
> Cloudstack instance or secondary storage but can be accessed by virtual 
> machines being migrated to this rack).
> 1000-2000 -- VLAN's that exist in my top of rack switch on the Cloudstack 
> rack and assigned to my trunk ports to the cloud servers but routed nowhere 
> else, for VPC's and such. 
> 
> Stuck with VLAN's rather than one of the SDN modules like VXNET because a) 
> it's the oldest and most likely to be stable, b) compatible with my 
> already-existing network hardware and networks (wouldn't have to somehow map 
> a VLAN to a SDN virtual network to reach 192 or 200 or create a public 102), 
> and c) least complex to set up and configure given my existing top-of-rack 
> switch that does VLANs just fine.
> 
> Okay, here's how I had to configure Centos 7 to make it work: 
> 
> enp4s[01] -> bond0 -> bond0.100 -> br100  -- had to create two interface 
> files, add them to bond0 bridge, then create a bond0.100 vlan interface, then 
> a br100 bridge,  for my management network. In
> /etc/sysconfig-network-scripts: 
> 
> # ls ifcfg-*
> ifcfg-bond0 ifcfg-bond0.100 ifcfg-br100 ifcfg-enp4s0 ifcfg-enp4s1
> 
> (where 4s0 and 4s1 are my 10 gigabit Ethernets).
> 
> Don't create anything else. You'll just confuse Cloudstack. Any other 
> configuration of the network simply fails to work. In particular, creating 
> br101 etc. fails because CloudStack wants to create its own VLANs and  
> bridges and if you traffic label it as br101 it'll try making vlan br101.101 
> (doesn't work, duh). Yes, I know this contradicts every single piece of 
> advice I've seen on this list. All I know is that this is what works, while 
> every other piece of advice I've seen for labeling the public and private 
> guest networking fails. 
> 
> When creating the networks in the GUI under Advanced networking, set bond0 as 
> your physical network and br100 as the KVM traffic label for the Management 
> network and Storage network and give them addresses with VLAN 100 (assuming 
> you're using the same network for both management and storage networks, which 
> is what makes sense with my single 10gbit pipe), but do *not* set up anything 
> as a traffic label for Guest or Public networks. You will confuse the agent 
> greatly. Let it use the default labels. It'll work. It'll set 

AW: Creating a Cloud-Init Ready Template for CentOS7

[S . Brüseke - proIO GmbH]

Hi,

we are using the following config for template createn via virt-install:
https://gitlab.proio.com/s.brueseke/megonacloudtemplates/blob/master/CentOS/centos7.cfg

But take a look at: http://dl.openvm.eu/
You can find tempates there.

Mit freundlichen Grüßen / With kind regards,

Swen

-Ursprüngliche Nachricht-
Von: Imran Ahmed [mailto:im...@eaxiom.net] 
Gesendet: Donnerstag, 3. August 2017 18:13
An: users@cloudstack.apache.org
Betreff: Creating a Cloud-Init Ready Template for CentOS7

Hi all,

Can someone suggest what packages are recommended to create a new cloud-init 
enabled template for CentOS 7?
For an OpenStack environment we need below packages:
acpid
Cloud-init
cloud-utils-growpart

Also  on the host machine we use virt-sysprep  to remove mac addresses etc.

Regards,

Imran



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: Creating a Cloud-Init Ready Template for CentOS7

[Rodrigo Baldasso]

http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/templates.html#creating-a-linux-template

You can install qemu-guest-agent if you use KVM. 



- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 03/08/2017 13:13:22, Imran Ahmed  wrote:
Hi all,

Can someone suggest what packages are recommended to create a new cloud-init
enabled template for CentOS 7?
For an OpenStack environment we need below packages:
acpid
Cloud-init
cloud-utils-growpart

Also on the host machine we use virt-sysprep to remove mac addresses etc.

Regards,

Imran

Creating a Cloud-Init Ready Template for CentOS7

[Imran Ahmed]

Hi all,

Can someone suggest what packages are recommended to create a new cloud-init
enabled template for CentOS 7?
For an OpenStack environment we need below packages:
acpid
Cloud-init
cloud-utils-growpart

Also  on the host machine we use virt-sysprep  to remove mac addresses etc.

Regards,

Imran

Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Rohit Yadav]

All,


We've helped with several PR reviews and merges recently, both in 4.9 and 
master.

We'll stop accepting any changes by end of next week (18 August), afterwards 
we'll only accept test and blocker fixes blocking the release.


Feel free to suggest any commits/fixes/PRs we should consider towards 4.9.3.0.


Following satisfactory test results (both Travis, Trillian and others) on 4.9 
branch we'll cut 4.9.3.0 RC1 for voting.


Regards.


From: Sean Lair 
Sent: Tuesday, July 25, 2017 1:05:56 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)

Hi Rohit

I previous suggested these for 4.9.3.0

https://github.com/apache/cloudstack/pull/2041 (VR related jobs scheduled and 
run twice on mgmt servers)
https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of S2S VPNs - 
also exists in 4.10)
https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work after 
vRouter reboot)

I'd also like to suggest these:
https://github.com/apache/cloudstack/pull/1246 (unable to use reserved IP range 
in a network)
https://github.com/apache/cloudstack/pull/2201 (VPC VR doesn't respond to DNS 
requests from remote access vpn clients)


Thanks
Sean

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Monday, July 24, 2017 5:56 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

All,


We'll accept bugfixes on 4.9 branch till end of next week, following which I'll 
start release work towards 4.9.3.0 (LTS) release. Please help review 
outstanding PRs, share PRs that we should consider and advise/suggest issues 
that need to be reverted/backported, for example see: 
https://github.com/apache/cloudstack/pull/2052


Thank you for your support and co-operation.


- Rohit


From: Rohit Yadav 
Sent: Sunday, July 23, 2017 1:26:48 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

All,


I've started looking into reviewing/testing/merging of the PRs targeting 4.9+, 
I'll share some plans around 4.9.3.0 soon. Meanwhile, help in reporting any 
major/critical bugs and PRs we should consider reviewing/testing/merging. 
Thanks.


- Rohit

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue




rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue

RE: Instance with a larger disk size then Template

[Rodrigo Baldasso]

We don't use lvm inside containers here because we find out that is easier to 
resize without it. 

You can even boot up with an GParted ISO that's makes very simple resizing the 
VM (even the client can do it) with very small risk comparing to use manual 
tools.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 03/08/2017 10:41:00, Imran Ahmed  wrote:
Hi Erik,

Thanks for suggestion, I tried this too and was successful till lvextending the 
logical volume. However at the stage of running resize2fs it produced errors 
like : Bad super block..." so I ended up installing from an ISO and 
partitioning without LVM this time so that I could use this template to resize 
in future.

Cheers,

Imran

-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: Thursday, August 03, 2017 3:56 PM
To: users@cloudstack.apache.org
Subject: Re: Instance with a larger disk size then Template

A faster approach than those mentioned is to create a new partition on
the unused disk space, and add it to the volume group, then use
lvextend and resizing the fs.

On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed wrote:
> Hi All,
>
> I am creating an instance with a 300GB disk from a CentOS 7 template that
> has 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance still
> shows 5GB .
>
> The device size (/dev/vda) however shows 300GB. The question is what is
> the best strategy to resize the root LVM partition so that I could use all
> 300G.
>
> Kind regards,
>
> Imran
>

RE: Instance with a larger disk size then Template

[Imran Ahmed]

Hi Erik,

Thanks for suggestion, I tried this too and was successful till lvextending the 
logical volume. However at the stage of running resize2fs  it produced errors 
like : Bad super block..."  so I ended up installing from an ISO and 
partitioning without LVM this time so that I could use this template to resize 
in future.

Cheers,

Imran 

-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com] 
Sent: Thursday, August 03, 2017 3:56 PM
To: users@cloudstack.apache.org
Subject: Re: Instance with a larger disk size then Template

A faster approach than those mentioned is to create a new partition on
the unused disk space, and add it to the volume group, then use
lvextend and resizing the fs.

On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed  wrote:
> Hi All,
>
> I am creating an instance with a 300GB disk from a CentOS 7 template that
> has 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance  still
> shows 5GB .
>
> The device size  (/dev/vda) however shows 300GB.  The question is what is
> the best strategy to resize the root LVM partition so that I could use all
> 300G.
>
> Kind regards,
>
> Imran
>

Re: Instance with a larger disk size then Template

[Erik Weber]

A faster approach than those mentioned is to create a new partition on
the unused disk space, and add it to the volume group, then use
lvextend and resizing the fs.

On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed  wrote:
> Hi All,
>
> I am creating an instance with a 300GB disk from a CentOS 7 template that
> has 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance  still
> shows 5GB .
>
> The device size  (/dev/vda) however shows 300GB.  The question is what is
> the best strategy to resize the root LVM partition so that I could use all
> 300G.
>
> Kind regards,
>
> Imran
>

Re: Instance with a larger disk size then Template

[Dag Sonstebo]

Hi Imran,

If you create a VM from template then the root disk adopts the size of the 
original template – and the disk size your select is for *additional data 
disks*. So you probably now how a 5GB root disk and a 300GB data disk attached.

In that case you should no use LVM to extend the root partition if you ever 
want to rely on volume snapshots. There is no mechanism in CloudStack to 
exactly time snapshots of two disks part of the same volume group – hence you 
can never use this for recovery.

All in all CloudStack works on the premise that your VM system volume resides 
on a single disk – hence you will run into problems if you go outside these 
boundaries. Your best bet is to either 1) build from ISO and select the 300GB 
disk – which will now apply to the root disk, or 2) resize your root disk and 
use the LVM processes described in the other emails to expand into the free 
space.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 03/08/2017, 11:15, "Imran Ahmed"  wrote:

Hi Dag,

Thanks for  your prompt reply.   During the creation of new instance I set 
the size of root disk to 300G. Once the instance was created , the device 
/dev/vda was created with 300G size.  However the LVM partition still shows 5G 
size.  (same is shown under in df -h)

Regards,

Imran  

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Thursday, August 03, 2017 3:08 PM
To: users@cloudstack.apache.org
Subject: Re: Instance with a larger disk size then Template

Hi Imran,

Can you elaborate – you say your template had a 5GB root disk. Did you 
resize this, or did you add a disk?

If you resized it then all you need to do is use your LVM and filesystem 
tools to expand your partition. 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 03/08/2017, 11:00, "Imran Ahmed"  wrote:

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template 
that
has 5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  
still
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what 
is
the best strategy to resize the root LVM partition so that I could use 
all
300G.

Kind regards,

Imran 




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 





dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

RE: Instance with a larger disk size then Template

[Imran Ahmed]

Hi Swen,

I am thankful for the detailed technical explanation. I will try to expand
the LVM partition by booting from the CentOS CD and will come back to  you
if I need further support.

Cheers,

Imran 

-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com] 
Sent: Thursday, August 03, 2017 3:18 PM
To: users@cloudstack.apache.org
Subject: AW: Instance with a larger disk size then Template

Hi Imran,

you are talking about 3 different levels here to reach your goal of resizing
a volume. First level is the volume itself. This is what you can do within
CS. After that you need to extend the partition and then you need to expand
the filesystem. The last to levels you need to do within the os of the
server.

What we do is using cloud-init within our template to automate this. But our
templates do not use LVM. Our templates are checking at boot if the root
volume has been extended and expanding the partition and the filesystem.

If you want to know more about it, I can give you more details.

Mit freundlichen Grüßen / With kind regards,

Swen Brüseke

-Ursprüngliche Nachricht-
Von: Imran Ahmed [mailto:im...@eaxiom.net] 
Gesendet: Donnerstag, 3. August 2017 12:00
An: users@cloudstack.apache.org
Betreff: Instance with a larger disk size then Template

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template that
has 5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  still
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what is
the best strategy to resize the root LVM partition so that I could use all
300G.

Kind regards,

Imran 



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind
nicht gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in
error) please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. 

RE: Instance with a larger disk size then Template

[Imran Ahmed]

Hi Makran,
I appreciate your reply on this. I will complete the procedure that you have 
mentioned.

Kind regards,
Imran

-Original Message-
From: Makrand [mailto:makrandsa...@gmail.com] 
Sent: Thursday, August 03, 2017 3:10 PM
To: users@cloudstack.apache.org
Subject: Re: Instance with a larger disk size then Template

Imran,

>From Linux POV, boot VM from live centos DVD/ISO and then go on for
extending root LVM partition. Once you boot into live ISO, the existing
root will be just another lvm and can be extended by using existing unused
space on vggroup.

If you don't wanna do all time with new VM, then set correct root partition
size for new VM, take snap of root and get new template form this and use
it in future

--
Makrand


On Thu, Aug 3, 2017 at 3:30 PM, Imran Ahmed  wrote:

> Hi All,
>
> I am creating an instance with a 300GB disk from a CentOS 7 template that
> has 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance  still
> shows 5GB .
>
> The device size  (/dev/vda) however shows 300GB.  The question is what is
> the best strategy to resize the root LVM partition so that I could use all
> 300G.
>
> Kind regards,
>
> Imran
>
>

AW: Instance with a larger disk size then Template

[S . Brüseke - proIO GmbH]

Hi Imran,

you are talking about 3 different levels here to reach your goal of resizing a 
volume. First level is the volume itself. This is what you can do within CS. 
After that you need to extend the partition and then you need to expand the 
filesystem. The last to levels you need to do within the os of the server.

What we do is using cloud-init within our template to automate this. But our 
templates do not use LVM. Our templates are checking at boot if the root volume 
has been extended and expanding the partition and the filesystem.

If you want to know more about it, I can give you more details.

Mit freundlichen Grüßen / With kind regards,

Swen Brüseke

-Ursprüngliche Nachricht-
Von: Imran Ahmed [mailto:im...@eaxiom.net] 
Gesendet: Donnerstag, 3. August 2017 12:00
An: users@cloudstack.apache.org
Betreff: Instance with a larger disk size then Template

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template that has 
5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  still 
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what is the 
best strategy to resize the root LVM partition so that I could use all 300G.

Kind regards,

Imran 



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

RE: Instance with a larger disk size then Template

[Imran Ahmed]

Hi Dag,

Thanks for  your prompt reply.   During the creation of new instance I set the 
size of root disk to 300G. Once the instance was created , the device /dev/vda 
was created with 300G size.  However the LVM partition still shows 5G size.  
(same is shown under in df -h)

Regards,

Imran  

-Original Message-
From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] 
Sent: Thursday, August 03, 2017 3:08 PM
To: users@cloudstack.apache.org
Subject: Re: Instance with a larger disk size then Template

Hi Imran,

Can you elaborate – you say your template had a 5GB root disk. Did you resize 
this, or did you add a disk?

If you resized it then all you need to do is use your LVM and filesystem tools 
to expand your partition. 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 03/08/2017, 11:00, "Imran Ahmed"  wrote:

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template that
has 5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  still
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what is
the best strategy to resize the root LVM partition so that I could use all
300G.

Kind regards,

Imran 




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Instance with a larger disk size then Template

[Makrand]

Imran,

>From Linux POV, boot VM from live centos DVD/ISO and then go on for
extending root LVM partition. Once you boot into live ISO, the existing
root will be just another lvm and can be extended by using existing unused
space on vggroup.

If you don't wanna do all time with new VM, then set correct root partition
size for new VM, take snap of root and get new template form this and use
it in future

--
Makrand


On Thu, Aug 3, 2017 at 3:30 PM, Imran Ahmed  wrote:

> Hi All,
>
> I am creating an instance with a 300GB disk from a CentOS 7 template that
> has 5GB disk (LVM Based).
> The issue is that the root LVM partition inside the new VM instance  still
> shows 5GB .
>
> The device size  (/dev/vda) however shows 300GB.  The question is what is
> the best strategy to resize the root LVM partition so that I could use all
> 300G.
>
> Kind regards,
>
> Imran
>
>

Re: Instance with a larger disk size then Template

[Dag Sonstebo]

Hi Imran,

Can you elaborate – you say your template had a 5GB root disk. Did you resize 
this, or did you add a disk?

If you resized it then all you need to do is use your LVM and filesystem tools 
to expand your partition. 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 03/08/2017, 11:00, "Imran Ahmed"  wrote:

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template that
has 5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  still
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what is
the best strategy to resize the root LVM partition so that I could use all
300G.

Kind regards,

Imran 




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Instance with a larger disk size then Template

[Imran Ahmed]

Hi All,

I am creating an instance with a 300GB disk from a CentOS 7 template that
has 5GB disk (LVM Based).
The issue is that the root LVM partition inside the new VM instance  still
shows 5GB .  

The device size  (/dev/vda) however shows 300GB.  The question is what is
the best strategy to resize the root LVM partition so that I could use all
300G.

Kind regards,

Imran 

RE: CloudStack 4.9 Enabling Local Storage for Zones

[Imran Ahmed]

Hi Anshul,

Got your point.

Thanks a lot 

Regards,
Imran

-Original Message-
From: Anshul Gangwar [mailto:anshul.gang...@accelerite.com] 
Sent: Thursday, August 03, 2017 1:59 PM
To: users@cloudstack.apache.org
Subject: Re: CloudStack 4.9 Enabling Local Storage for Zones

Full path is Home->Infrastructure->Zone-> 

Regards,
Anshul 

On 03/08/17, 2:27 PM, "Anshul Gangwar"  wrote:

It’s not that kind of setting. 

Goto Zone →→Details

Go through all the details. There you will see “Enable local storage for 
User VMs”. Modify details to change the value.

Regards,
Anshul 

On 03/08/17, 2:17 PM, "Imran Ahmed"  wrote:

Hi Anshul,

Thanks for your reply.

 

Can you specify the setting parameter? All I can see under settings for 
a zone are below :

 

1.  enable.dynamic.scale.vm Enables/Disables dynamically scaling a vm 

2.  guest.domain.suffix Default domain name for vms inside 
virtualized networks fronted by router

3.  minreq.sysvmtemplate.version  What version should the Virtual 
Routers report

4.  network.router.EnableServiceMonitoringservice monitoring in 
router enable/disable option, 

5.  network.throttling.rate Default data transfer rate in megabits per 
second allowed in network.

6.  pool.storage.allocated.capacity.disablethreshold  Percentage 
(as a value between 0 and 1) of allocated storage utilization above which 
allocators will disable using the pool for low allocated storage available.

7.  pool.storage.capacity.disablethresholdPercentage (as a value 
between 0 and 1) of storage utilization above which allocators will disable 
using the pool for low storage available. 

8.  system.vm.use.local.storage   Indicates whether to use local 
storage pools or shared storage pools for system VMs.   

9.  use.external.dns  Bypass internal dns, use external dns1 and dns2 

 

 

regards,

 

Imran

 

-Original Message-
From: Anshul Gangwar [mailto:anshul.gang...@accelerite.com] 
Sent: Thursday, August 03, 2017 1:32 PM
To: users@cloudstack.apache.org
Subject: Re: CloudStack 4.9 Enabling Local Storage for Zones

 

That option is available in zone details. 

 

Regards,

Anshul 

 

On 03/08/17, 1:16 PM, "Imran Ahmed"  wrote:

 

Hello All,

I am working on a cloudstack 4.9 setup with a few KVM hosts. Some 
of the KVM

hosts have local primary storage besides the NFS storage.

In the global settings I could not find an option to enable local 
storage

for the zone. ( I am using advanced zone here).

When I tried to create a VM instance on the local storage, it gave 
an error

saying something like " Local storage is not enabled for the 
zone"

To resolve this issue, I had to manually enable the local storage 
setting in

the database as below:



update data_center set is_local_storage_enabled = 1 where id =

;





I wonder why this option is not available on the GUI under global 
settings..







Thanks and regards,



Imran





 

DISCLAIMER

==

This e-mail may contain privileged and confidential information which 
is the property of Accelerite, a Persistent Systems business. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: CloudStack 4.9 Enabling Local Storage for Zones

[Anshul Gangwar]

Full path is Home->Infrastructure->Zone-> 

Regards,
Anshul 

On 03/08/17, 2:27 PM, "Anshul Gangwar"  wrote:

It’s not that kind of setting. 

Goto Zone →→Details

Go through all the details. There you will see “Enable local storage for 
User VMs”. Modify details to change the value.

Regards,
Anshul 

On 03/08/17, 2:17 PM, "Imran Ahmed"  wrote:

Hi Anshul,

Thanks for your reply.

 

Can you specify the setting parameter? All I can see under settings for 
a zone are below :

 

1.  enable.dynamic.scale.vm Enables/Disables dynamically scaling a vm 

2.  guest.domain.suffix Default domain name for vms inside 
virtualized networks fronted by router

3.  minreq.sysvmtemplate.version  What version should the Virtual 
Routers report

4.  network.router.EnableServiceMonitoringservice monitoring in 
router enable/disable option, 

5.  network.throttling.rate Default data transfer rate in megabits per 
second allowed in network.

6.  pool.storage.allocated.capacity.disablethreshold  Percentage 
(as a value between 0 and 1) of allocated storage utilization above which 
allocators will disable using the pool for low allocated storage available.

7.  pool.storage.capacity.disablethresholdPercentage (as a value 
between 0 and 1) of storage utilization above which allocators will disable 
using the pool for low storage available. 

8.  system.vm.use.local.storage   Indicates whether to use local 
storage pools or shared storage pools for system VMs.   

9.  use.external.dns  Bypass internal dns, use external dns1 and dns2 

 

 

regards,

 

Imran

 

-Original Message-
From: Anshul Gangwar [mailto:anshul.gang...@accelerite.com] 
Sent: Thursday, August 03, 2017 1:32 PM
To: users@cloudstack.apache.org
Subject: Re: CloudStack 4.9 Enabling Local Storage for Zones

 

That option is available in zone details. 

 

Regards,

Anshul 

 

On 03/08/17, 1:16 PM, "Imran Ahmed"  wrote:

 

Hello All,

I am working on a cloudstack 4.9 setup with a few KVM hosts. Some 
of the KVM

hosts have local primary storage besides the NFS storage.

In the global settings I could not find an option to enable local 
storage

for the zone. ( I am using advanced zone here).

When I tried to create a VM instance on the local storage, it gave 
an error

saying something like " Local storage is not enabled for the 
zone"

To resolve this issue, I had to manually enable the local storage 
setting in

the database as below:



update data_center set is_local_storage_enabled = 1 where id =

;





I wonder why this option is not available on the GUI under global 
settings..







Thanks and regards,



Imran





 

DISCLAIMER

==

This e-mail may contain privileged and confidential information which 
is the property of Accelerite, a Persistent Systems business. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: CloudStack 4.9 Enabling Local Storage for Zones

[Anshul Gangwar]

It’s not that kind of setting. 

Goto Zone →→Details

Go through all the details. There you will see “Enable local storage for User 
VMs”. Modify details to change the value.

Regards,
Anshul 

On 03/08/17, 2:17 PM, "Imran Ahmed"  wrote:

Hi Anshul,

Thanks for your reply.

 

Can you specify the setting parameter? All I can see under settings for a 
zone are below :

 

1.  enable.dynamic.scale.vm Enables/Disables dynamically scaling a vm 

2.  guest.domain.suffix Default domain name for vms inside virtualized 
networks fronted by router

3.  minreq.sysvmtemplate.version  What version should the Virtual Routers 
report

4.  network.router.EnableServiceMonitoringservice monitoring in router 
enable/disable option, 

5.  network.throttling.rate Default data transfer rate in megabits per 
second allowed in network.

6.  pool.storage.allocated.capacity.disablethreshold  Percentage (as a 
value between 0 and 1) of allocated storage utilization above which allocators 
will disable using the pool for low allocated storage available.

7.  pool.storage.capacity.disablethresholdPercentage (as a value 
between 0 and 1) of storage utilization above which allocators will disable 
using the pool for low storage available. 

8.  system.vm.use.local.storage   Indicates whether to use local storage 
pools or shared storage pools for system VMs.   

9.  use.external.dns  Bypass internal dns, use external dns1 and dns2 

 

 

regards,

 

Imran

 

-Original Message-
From: Anshul Gangwar [mailto:anshul.gang...@accelerite.com] 
Sent: Thursday, August 03, 2017 1:32 PM
To: users@cloudstack.apache.org
Subject: Re: CloudStack 4.9 Enabling Local Storage for Zones

 

That option is available in zone details. 

 

Regards,

Anshul 

 

On 03/08/17, 1:16 PM, "Imran Ahmed"  wrote:

 

Hello All,

I am working on a cloudstack 4.9 setup with a few KVM hosts. Some of 
the KVM

hosts have local primary storage besides the NFS storage.

In the global settings I could not find an option to enable local 
storage

for the zone. ( I am using advanced zone here).

When I tried to create a VM instance on the local storage, it gave an 
error

saying something like " Local storage is not enabled for the zone"

To resolve this issue, I had to manually enable the local storage 
setting in

the database as below:



update data_center set is_local_storage_enabled = 1 where id =

;





I wonder why this option is not available on the GUI under global 
settings..







Thanks and regards,



Imran





 

DISCLAIMER

==

This e-mail may contain privileged and confidential information which is 
the property of Accelerite, a Persistent Systems business. It is intended only 
for the use of the individual or entity to which it is addressed. If you are 
not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

RE: CloudStack 4.9 Enabling Local Storage for Zones

[Imran Ahmed]

Hi Anshul,

Thanks for your reply.

 

Can you specify the setting parameter? All I can see under settings for a zone 
are below :

 

1.  enable.dynamic.scale.vm Enables/Disables dynamically scaling a vm 

2.  guest.domain.suffix Default domain name for vms inside virtualized 
networks fronted by router

3.  minreq.sysvmtemplate.version  What version should the Virtual Routers 
report

4.  network.router.EnableServiceMonitoringservice monitoring in router 
enable/disable option, 

5.  network.throttling.rate Default data transfer rate in megabits per second 
allowed in network.

6.  pool.storage.allocated.capacity.disablethreshold  Percentage (as a 
value between 0 and 1) of allocated storage utilization above which allocators 
will disable using the pool for low allocated storage available.

7.  pool.storage.capacity.disablethresholdPercentage (as a value between 0 
and 1) of storage utilization above which allocators will disable using the 
pool for low storage available. 

8.  system.vm.use.local.storage   Indicates whether to use local storage pools 
or shared storage pools for system VMs.   

9.  use.external.dns  Bypass internal dns, use external dns1 and dns2 

 

 

regards,

 

Imran

 

-Original Message-
From: Anshul Gangwar [mailto:anshul.gang...@accelerite.com] 
Sent: Thursday, August 03, 2017 1:32 PM
To: users@cloudstack.apache.org
Subject: Re: CloudStack 4.9 Enabling Local Storage for Zones

 

That option is available in zone details. 

 

Regards,

Anshul 

 

On 03/08/17, 1:16 PM, "Imran Ahmed"  wrote:

 

Hello All,

I am working on a cloudstack 4.9 setup with a few KVM hosts. Some of the KVM

hosts have local primary storage besides the NFS storage.

In the global settings I could not find an option to enable local storage

for the zone. ( I am using advanced zone here).

When I tried to create a VM instance on the local storage, it gave an error

saying something like " Local storage is not enabled for the zone"

To resolve this issue, I had to manually enable the local storage setting in

the database as below:



update data_center set is_local_storage_enabled = 1 where id =

;





I wonder why this option is not available on the GUI under global settings..







Thanks and regards,



Imran





 

DISCLAIMER

==

This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

UNSUBCRIBE

[Akshay Dhapare]

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: CloudStack 4.9 Enabling Local Storage for Zones

[Anshul Gangwar]

That option is available in zone details. 

Regards,
Anshul 

On 03/08/17, 1:16 PM, "Imran Ahmed"  wrote:

Hello All,
I am working on a cloudstack 4.9 setup with a few KVM hosts. Some of the KVM
hosts have local primary storage besides the NFS storage.
In the global settings I could not find an option to enable local storage
for the zone. ( I am using advanced zone here).
When I tried to create a VM instance on the local storage, it gave an error
saying something like " Local storage is not enabled for the zone"
To resolve this issue, I had to manually enable the local storage setting in
the database as below:

update data_center set is_local_storage_enabled = 1 where id =
;


I wonder why this option is not available on the GUI under global settings..



Thanks and regards,

Imran



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

CloudStack 4.9 Enabling Local Storage for Zones

[Imran Ahmed]

Hello All,
I am working on a cloudstack 4.9 setup with a few KVM hosts. Some of the KVM
hosts have local primary storage besides the NFS storage.
In the global settings I could not find an option to enable local storage
for the zone. ( I am using advanced zone here).
When I tried to create a VM instance on the local storage, it gave an error
saying something like " Local storage is not enabled for the zone"
To resolve this issue, I had to manually enable the local storage setting in
the database as below:

update data_center set is_local_storage_enabled = 1 where id =
;


I wonder why this option is not available on the GUI under global settings..



Thanks and regards,

Imran