Windows Virtual Machine on Cloudstack KVM Platform
HI Is there anybody running Windows on Cloudstack KVM platform, is there any performance issue ? For Cloudstack KVM, running Windows, how can I know is using VirtIO driver or not ? Seems I not able to choose if to use VirtIO or not . Thank you. -- Regards, Hean Seng
Re: Best practises and ideas for power outtake scenarios
Hi Chris, shutting down ACS VMs and hosts is just one part of the story, another part of the story is also shutting down your side infra, such as storage arrays, and any external stuff you might have. But let's focus on ACS. I would make some scripting which involves: - pulling data from UPS to detect when power down, sleep for some short amount of time (i.e. 1-2minute to see if this is some hiccup) then if power is still down, you can use bash and cloudmonkey to automate the following (to be tested properly in your test env): - Disable the zone(s) - Put all Primary Storages in the Maintenance mode - this will cause all existing VMs on that storage to be shutdown, one by one = takes LONG time SO better approach is to query ACS for a list of running VMs (save this in a file somewhere for later!), put that list in a file, send VM stop command in batches of 10 or 20 or 50 (depending on the size and speed of your storage) - don't overload the storage confirm all your user VMs are stopped stop all system VMs (SSVM, CPVM, all VRs) --- confirm no running VM -- at this point there is no VM running at all in your ACS setup -- shutdown management server (so you avoid putting your hosts in maintenance mode in ACS - takes time otherwise), shutdown your MySQL servers (use by ACS mgmt servers) -- if using VMware, put all hosts in maintenance mode, and ask Center to shutdown all hosts (you need to see what to do with vCenter itself, etc) -- if other hypervisors are used (KVM, XenServer) - do whatever it takes to shut them down safely/correctly When power is up, reverse everything - power hosts, wait some time and confirm all your hosts are up/connected in your management tools ( e.g. in vCenter, XenCenter, KVM via VirtManager, whatever) Start the MySQL, the mgmt server, enable the zone (SSVM and CPVM will be started automatically), then query that list of previously running VMS (that you saved) and start them one by one, or in batches of 5 or 10 (or more) - depending on your HW performance (try to avoid "boot storm) - starting a VM in a network will cause VRs to be started automatically, so this step is not needed explicitely - but you can handle it manually as well if you like This is just to give you an idea (I once had to shutdown ACS and everything else, which included SolidFire storage, Cloudian S3 cluster, some other storage solutions etc, in my ex company) - was a really "interesting" experience... Best, On Thu, 3 Jun 2021 at 18:21, vas...@gmx.de wrote: > Hello everyone, > > i would like to ask for some ideas / bestpractises for dealing with > power outtake scenarios involving the the cloudstack infrastructure. > So the usecase would be a power outtake at a datacenter where all > components of cloudstack (management server, hosts, storage) are > hosted, which can't be repaired in a given time. > > so the "simple" target process would be something like this: > > 1.Power outtake detected bei UPS > 2. UPS is giving notification to CS Management > 3. CS management is sending information to all vm's as well as hosts > 4. vm's and hosts performing gracefull shutdown > 5. management server performs gracefull shutdown > 6. afterwards shutdown of storage and further components > > Are there any included "workflows" or mechanics which can be used out > of the box? Any real-life best practices how to implement this kind of > workflow? > > with regards, > Chris > -- Andrija Panić
Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1)
Hi Rohit, I tested also on 4.15.1.0 RC1 and it fails; same issue as the one raised in 4.15.0.0. Regards, Gabriel On Thu, Jun 3, 2021, 11:20 Rohit Yadav wrote: > Hi Gabriel, > > Have you tested the issue on 4.15.1.0 RC1? Do existing VXLAN based > networks work post upgrading to 4.15.1.0 RC1? > > If this is indeed a blocker issue, I'm happy to cut another RC next week > after the current RC's voting window. Meanwhile all PMCs, committers and > users may continue to test, vote RC1. Thanks. > > > Regards. > > > From: Gabriel Bräscher > Sent: Thursday, June 3, 2021 19:26 > To: dev > Cc: Rohit Yadav ; users > Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1) > > Hi Rohit, > > Thanks for bringing RC1. > I am afraid that we will need an RC2. We are facing an issue that might be > a blocker. > > I've just opened the issue here: > https://github.com/apache/cloudstack/issues/5071 > In a nutshell, we are not able to create a network when using VXLAN due to > a validation added in 4.15.0.0 that explicitly checks for "VLAN" at the > broadcast URI. > > Regards, > Gabriel. > > > Em qui., 3 de jun. de 2021 às 04:37, Wido den Hollander > escreveu: > > > +1 (binding) > > > > On 6/2/21 11:50 AM, Rohit Yadav wrote: > > > Hi All, > > > > > > I've created a 4.15.1.0 release, with the following artifacts up for a > > vote: > > > > > > Git Branch and Commit SHA: > > > https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210602T1429 > > > Commit: aaac4b17099ba838a3f7b57400277ca9b23f98f5 > > > > > > Source release (checksums and signatures are available at the same > > > location): > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/ > > > > > > PGP release keys (signed using > 5ED1E1122DC5E8A4A45112C2484248210EE3D884): > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > > > The vote will be open for 120 hours, until 7 June 2021. > > > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate > > > "(binding)" with their vote? > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove (and reason why) > > > > > > For users convenience, the packages from this release candidate (RC1) > and > > > 4.15.1 systemvmtemplates are available here: > > > https://download.cloudstack.org/testing/4.15.1.0-RC1/ > > > https://download.cloudstack.org/systemvm/4.15/ > > > > > > Documentation is not published yet, but the following may be referenced > > for > > > upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be > > > registered prior to upgrade) > > > > > > https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade > > > > > > Regards. > > > > > > > > >
Best practises and ideas for power outtake scenarios
Hello everyone, i would like to ask for some ideas / bestpractises for dealing with power outtake scenarios involving the the cloudstack infrastructure. So the usecase would be a power outtake at a datacenter where all components of cloudstack (management server, hosts, storage) are hosted, which can't be repaired in a given time. so the "simple" target process would be something like this: 1.Power outtake detected bei UPS 2. UPS is giving notification to CS Management 3. CS management is sending information to all vm's as well as hosts 4. vm's and hosts performing gracefull shutdown 5. management server performs gracefull shutdown 6. afterwards shutdown of storage and further components Are there any included "workflows" or mechanics which can be used out of the box? Any real-life best practices how to implement this kind of workflow? with regards, Chris
Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1)
Hi Gabriel, Have you tested the issue on 4.15.1.0 RC1? Do existing VXLAN based networks work post upgrading to 4.15.1.0 RC1? If this is indeed a blocker issue, I'm happy to cut another RC next week after the current RC's voting window. Meanwhile all PMCs, committers and users may continue to test, vote RC1. Thanks. Regards. From: Gabriel Bräscher Sent: Thursday, June 3, 2021 19:26 To: dev Cc: Rohit Yadav ; users Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1) Hi Rohit, Thanks for bringing RC1. I am afraid that we will need an RC2. We are facing an issue that might be a blocker. I've just opened the issue here: https://github.com/apache/cloudstack/issues/5071 In a nutshell, we are not able to create a network when using VXLAN due to a validation added in 4.15.0.0 that explicitly checks for "VLAN" at the broadcast URI. Regards, Gabriel. Em qui., 3 de jun. de 2021 às 04:37, Wido den Hollander escreveu: > +1 (binding) > > On 6/2/21 11:50 AM, Rohit Yadav wrote: > > Hi All, > > > > I've created a 4.15.1.0 release, with the following artifacts up for a > vote: > > > > Git Branch and Commit SHA: > > https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210602T1429 > > Commit: aaac4b17099ba838a3f7b57400277ca9b23f98f5 > > > > Source release (checksums and signatures are available at the same > > location): > > https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/ > > > > PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884): > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > The vote will be open for 120 hours, until 7 June 2021. > > > > For sanity in tallying the vote, can PMC members please be sure to > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > For users convenience, the packages from this release candidate (RC1) and > > 4.15.1 systemvmtemplates are available here: > > https://download.cloudstack.org/testing/4.15.1.0-RC1/ > > https://download.cloudstack.org/systemvm/4.15/ > > > > Documentation is not published yet, but the following may be referenced > for > > upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be > > registered prior to upgrade) > > > https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade > > > > Regards. > > >
Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1)
Hi Rohit, Thanks for bringing RC1. I am afraid that we will need an RC2. We are facing an issue that might be a blocker. I've just opened the issue here: https://github.com/apache/cloudstack/issues/5071 In a nutshell, we are not able to create a network when using VXLAN due to a validation added in 4.15.0.0 that explicitly checks for "VLAN" at the broadcast URI. Regards, Gabriel. Em qui., 3 de jun. de 2021 às 04:37, Wido den Hollander escreveu: > +1 (binding) > > On 6/2/21 11:50 AM, Rohit Yadav wrote: > > Hi All, > > > > I've created a 4.15.1.0 release, with the following artifacts up for a > vote: > > > > Git Branch and Commit SHA: > > https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210602T1429 > > Commit: aaac4b17099ba838a3f7b57400277ca9b23f98f5 > > > > Source release (checksums and signatures are available at the same > > location): > > https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/ > > > > PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884): > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > The vote will be open for 120 hours, until 7 June 2021. > > > > For sanity in tallying the vote, can PMC members please be sure to > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > For users convenience, the packages from this release candidate (RC1) and > > 4.15.1 systemvmtemplates are available here: > > https://download.cloudstack.org/testing/4.15.1.0-RC1/ > > https://download.cloudstack.org/systemvm/4.15/ > > > > Documentation is not published yet, but the following may be referenced > for > > upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be > > registered prior to upgrade) > > > https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade > > > > Regards. > > >
RE: 2 networks with DHCP in the same subnet?
Ah I see now. Network A and B are shared so users cannot create them on their
own.
It seems shared networks cannot be hidden from accounts in the same domain in
advanced zone config (from the online documentation).
I will have to think this through.
Best regards,
Jordan
-Original Message-
From: Andrija Panic
Sent: Thursday, June 3, 2021 1:35 PM
To: users
Subject: Re: 2 networks with DHCP in the same subnet?
[X] This message came from outside your organization
Sounds like you are complicating the setup (or feel the need to do so, for
whatever reason).
Did you test:
parent domain with domain admin "admin" - then just regular users accounts
(QA/DEV) - so each QA and DEV can create their own resources (networks, VMs,
etc) - QA and DEV are separate accounts/tenants so can't access each other's
resources (i.e. different tenants) THe domain admin account for that domain
("admin" account), being the domain admin, should be able to manage resources
of all user's inside his own domain. - but if you provision a resource as ADMIN
user (domain admin user), those resources will be owned by ADMIN account only
(as expected) - so keep that in mind.
Best,
On Thu, 3 Jun 2021 at 11:04, Yordan Kostov wrote:
> Thank you Andrija,
>
> Indeed tested that, if ON "bypass vlan overlap" option, it is
> possible to create 2 shared networks in the same vlan.
> IP gets assigned but for some reason the interface is shutdown
> in some time(Ubuntu 20). I am now troubleshooting the reason for this.
>
> The design I am trying to create current is - 3 groups of
> users - lets call them QA and DEV and ADMIN teams.
> - Network A is for QAs.
> - Network B is for DEVs.
> - ADMIN should have access to both networks.
>
> I tried that setup with one parent domain (admins) and to child (QA
> and DEV). Assigning a network to child domain DEV hides the network from QA.
> ADMIN domain see the network but cannot create instances inside.
>
> If those 3 accounts are under one domain is it possible to:
> - assign Network A to be operated and visible only to QA and
> Admins
> - assign Network B to be operated and visible only to DEV and
> Admins
>
> The only solution I have found so far is the following:
> - Define 2 networks - A and B with VR (DHCP, DNS, USERDATA) only
> available to ADMINS so nobody sees them
> - Define L2 network AA with USERDATA assigned to QA that overlaps vlan
> id A
> - Define L2 network BB with USERDATA assigned to DEV that overlaps
> vlan id B
>
> Both users and admins can create instances. Users will not be able to
> change or choose IP address.
>
> Regards,
> Jordan
>
>
>
>
> -Original Message-
> From: Andrija Panic
> Sent: Thursday, June 3, 2021 10:38 AM
> To: users
> Subject: Re: 2 networks with DHCP in the same subnet?
>
>
> [X] This message came from outside your organization
>
>
> Considering you are trying to create 2 shared networks (irrelevant of
> their IP range), and I ASSUME you want them on the same VLAN? - then I
> don't think this alone is possible (2 network with the same VLAN)
>
> If you can do it, then it's easy to test what you are asking and
> have first hand-answer :)
>
> IN ACS workdl, in theory, 2 DHCP CAN operate in the same network,
> since ACS provisions explicit DHCP reservations for each IP - i.e. you
> can't just boot another VM (provisionined manually, outside ACS) in
> the same VLAN - as DHCP will reject to give it an IP.
>
> Best,
>
> On Wed, 2 Jun 2021 at 15:43, Yordan Kostov wrote:
>
> > Dear all,
> >
> > Is it possible to have one /24 network - for example
> > 10.10.10.0/24 where it is divided into 2 shared networks as follow:
> >
> > * Network A - 10.10.10.2-50 where 2 is Virtual router with DHCP for
> > the ip range mentioned
> > * Network B - 10.10.10.51-200 where 51 is Virtual router with DHCP
> for
> > the ip range mentioned
> >
> > I understand 2 DHCPs cannot operate in the same network but I was
> > wondering if this can be achieved somehow?
> >
> > Best regards,
> > Jordan
> >
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: 2 networks with DHCP in the same subnet?
Sounds like you are complicating the setup (or feel the need to do so, for
whatever reason).
Did you test:
parent domain with domain admin "admin" - then just regular users accounts
(QA/DEV) - so each QA and DEV can create their own resources (networks,
VMs, etc) - QA and DEV are separate accounts/tenants so can't access each
other's resources (i.e. different tenants)
THe domain admin account for that domain ("admin" account), being the
domain admin, should be able to manage resources of all user's inside his
own domain. - but if you provision a resource as ADMIN user (domain admin
user), those resources will be owned by ADMIN account only (as expected) -
so keep that in mind.
Best,
On Thu, 3 Jun 2021 at 11:04, Yordan Kostov wrote:
> Thank you Andrija,
>
> Indeed tested that, if ON "bypass vlan overlap" option, it is
> possible to create 2 shared networks in the same vlan.
> IP gets assigned but for some reason the interface is shutdown in
> some time(Ubuntu 20). I am now troubleshooting the reason for this.
>
> The design I am trying to create current is - 3 groups of users -
> lets call them QA and DEV and ADMIN teams.
> - Network A is for QAs.
> - Network B is for DEVs.
> - ADMIN should have access to both networks.
>
> I tried that setup with one parent domain (admins) and to child (QA and
> DEV). Assigning a network to child domain DEV hides the network from QA.
> ADMIN domain see the network but cannot create instances inside.
>
> If those 3 accounts are under one domain is it possible to:
> - assign Network A to be operated and visible only to QA and
> Admins
> - assign Network B to be operated and visible only to DEV and
> Admins
>
> The only solution I have found so far is the following:
> - Define 2 networks - A and B with VR (DHCP, DNS, USERDATA) only available
> to ADMINS so nobody sees them
> - Define L2 network AA with USERDATA assigned to QA that overlaps vlan id A
> - Define L2 network BB with USERDATA assigned to DEV that overlaps vlan id
> B
>
> Both users and admins can create instances. Users will not be able to
> change or choose IP address.
>
> Regards,
> Jordan
>
>
>
>
> -Original Message-
> From: Andrija Panic
> Sent: Thursday, June 3, 2021 10:38 AM
> To: users
> Subject: Re: 2 networks with DHCP in the same subnet?
>
>
> [X] This message came from outside your organization
>
>
> Considering you are trying to create 2 shared networks (irrelevant of
> their IP range), and I ASSUME you want them on the same VLAN? - then I
> don't think this alone is possible (2 network with the same VLAN)
>
> If you can do it, then it's easy to test what you are asking and have
> first hand-answer :)
>
> IN ACS workdl, in theory, 2 DHCP CAN operate in the same network, since
> ACS provisions explicit DHCP reservations for each IP - i.e. you can't just
> boot another VM (provisionined manually, outside ACS) in the same VLAN - as
> DHCP will reject to give it an IP.
>
> Best,
>
> On Wed, 2 Jun 2021 at 15:43, Yordan Kostov wrote:
>
> > Dear all,
> >
> > Is it possible to have one /24 network - for example
> > 10.10.10.0/24 where it is divided into 2 shared networks as follow:
> >
> > * Network A - 10.10.10.2-50 where 2 is Virtual router with DHCP for
> > the ip range mentioned
> > * Network B - 10.10.10.51-200 where 51 is Virtual router with DHCP
> for
> > the ip range mentioned
> >
> > I understand 2 DHCPs cannot operate in the same network but I was
> > wondering if this can be achieved somehow?
> >
> > Best regards,
> > Jordan
> >
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
KVM High Availability Regardless of Storage
Hello all, Today I am sharing one more video from the past CSEUGvirtual - a talk from our VP Gabriel Brascher. One of the great advantages of CloudStack is that it is vendor-independent, meaning you can decide the technology stack above and below based on your experience or needs. However, there is a limitation on CloudStack HA for KVM - it relies mainly on NFS heartbeat script checks. Gabriel’s talk illustrated how CloudStack HA works for KVM hosts and presented a way of improving its implementation in a way that KVM HA works with any storage system pluggable on KVM, not just NFS. https://youtu.be/3o_WdnPEyug Check the ACS Youtube Channel for more videos from the conference! Kind regards,
RE: 2 networks with DHCP in the same subnet?
Thank you Andrija, Indeed tested that, if ON "bypass vlan overlap" option, it is possible to create 2 shared networks in the same vlan. IP gets assigned but for some reason the interface is shutdown in some time(Ubuntu 20). I am now troubleshooting the reason for this. The design I am trying to create current is - 3 groups of users - lets call them QA and DEV and ADMIN teams. - Network A is for QAs. - Network B is for DEVs. - ADMIN should have access to both networks. I tried that setup with one parent domain (admins) and to child (QA and DEV). Assigning a network to child domain DEV hides the network from QA. ADMIN domain see the network but cannot create instances inside. If those 3 accounts are under one domain is it possible to: - assign Network A to be operated and visible only to QA and Admins - assign Network B to be operated and visible only to DEV and Admins The only solution I have found so far is the following: - Define 2 networks - A and B with VR (DHCP, DNS, USERDATA) only available to ADMINS so nobody sees them - Define L2 network AA with USERDATA assigned to QA that overlaps vlan id A - Define L2 network BB with USERDATA assigned to DEV that overlaps vlan id B Both users and admins can create instances. Users will not be able to change or choose IP address. Regards, Jordan -Original Message- From: Andrija Panic Sent: Thursday, June 3, 2021 10:38 AM To: users Subject: Re: 2 networks with DHCP in the same subnet? [X] This message came from outside your organization Considering you are trying to create 2 shared networks (irrelevant of their IP range), and I ASSUME you want them on the same VLAN? - then I don't think this alone is possible (2 network with the same VLAN) If you can do it, then it's easy to test what you are asking and have first hand-answer :) IN ACS workdl, in theory, 2 DHCP CAN operate in the same network, since ACS provisions explicit DHCP reservations for each IP - i.e. you can't just boot another VM (provisionined manually, outside ACS) in the same VLAN - as DHCP will reject to give it an IP. Best, On Wed, 2 Jun 2021 at 15:43, Yordan Kostov wrote: > Dear all, > > Is it possible to have one /24 network - for example > 10.10.10.0/24 where it is divided into 2 shared networks as follow: > > * Network A - 10.10.10.2-50 where 2 is Virtual router with DHCP for > the ip range mentioned > * Network B - 10.10.10.51-200 where 51 is Virtual router with DHCP for > the ip range mentioned > > I understand 2 DHCPs cannot operate in the same network but I was > wondering if this can be achieved somehow? > > Best regards, > Jordan > -- Andrija Panić
Re: Uploading Blog Post
Thanks Greg, Mark for replying. > The short answer is "downstream users should have the ability to > access both code and website sources". That implies that the website > source is in a version control system (git or svn) that can be used to > generate the website, just as much as they can fetch sources to build > the [Apache Cloudstack] releases. I understand the requirement for code and docs. May I ask why this is a requirement for the project website and blog? Is it any official ASF or ASF infra policy or simply a standard practice? Could the availability of posts DB/table synced to Git repo solve that in case of a CMS such as Wordpress or Drupal? > We have not found a way to post to Wordpress.com, sourced from version > control, so ... sorry to say: that is not a viable platform for the > primary website. If y'all can find a way to push from version control > over to wp.com, then yay! That would be great. I didn't find anything exactly but the following may be explored: https://github.com/deliciousbrains/wp-migrate-db https://wppusher.com/ https://wordpress.org/plugins/wp-github-sync/ But I hear that TLPs can get a wordpress instance on wordpress.com (instead of hosting/managing ourselves), if not for the full TLP website but at least as a separate blog (say on blog.cloudstack.apache.org)? Thanks. Regards. From: Greg Stein Sent: Monday, May 31, 2021 18:18 To: users@cloudstack.apache.org Cc: market...@cloudstack.apache.org Subject: Re: Uploading Blog Post On Mon, May 31, 2021 at 10:55:58AM +, Rohit Yadav wrote: > + users@infra (kindly, reply all so your email is visible to participants on > other mailing lists copied in this thread) users@infra is a private list, so I've removed it from this reply (mixing public/private lists is problematic) > Hi Infra, > > The Apache CloudStack (ACS) community is discussing options to > migrate the project website and blog to Wordpress [1] and the > consensus among the people on this thread is they want to go ahead > with this. Some attempts and discussions [2][3] were made in the past. In particular, please note Mark Thomas' point, and my acknowledgement at [1]. The short answer is "downstream users should have the ability to access both code and website sources". That implies that the website source is in a version control system (git or svn) that can be used to generate the website, just as much as they can fetch sources to build the [Apache Cloudstack] releases. We have not found a way to post to Wordpress.com, sourced from version control, so ... sorry to say: that is not a viable platform for the primary website. If y'all can find a way to push from version control over to wp.com, then yay! That would be great. > Before we go ahead with a PMC vote, I want to ask Infra if this is > technically feasible for the project website to be moved to Wordpress > which (a) may be hosted by ASF infra (preferably as a VM or service > much like other portals/website) Projects may use VMs for their primary websites, but (historically) Wordpress has had difficulties with self-hosting. As a result, the Foundation uses wordpress.com to host the Feathercast blog rather than attempting to self-host. Per above, if you can construct a process running on a VM, that pushes version control over to WP.com, then that problem is solved. (and yes, the Foundation would be fine paying the yearly fee to host at wp.com; that isn't a concern) > or (b) by an external Wordpress > hosting service which is under the control of ACS PMC. As I understand > this will require the content to be migrated to a Wordpress instance > (either option-a or option-b) and for ASF infra to update the > CNAME/dns record. Per the linked email, the primary concern is the ability for downstream users to be able to view/construct all the content of an Apache product's website. > Out of curiosity - are there any other projects that have their > websites/blogs based on a CMS (a not static website builds), say > Wordpress, Drupal etc. There are many projects currently using Pelican, sourced from a git repository, to translate Github-Flavored Markdown files to HTML static content. This is the Infra-recommended process/workflow for website publishing. Please see https://infra.apache.org/project-site.html We recommend this workflow as it allows content-editors to use github.com to edit/preview pages very simply, and those changes will quickly appear on the website when saved. Best regards, Greg Stein Infrastructure Administrator, ASF [1] https://lists.apache.org/thread.html/6ec3ff74167a7feac0bd5ee6b4361deb0bea9eb8018df5a3a923b10f%40%3Clegal-discuss.apache.org%3E
Re: 2 networks with DHCP in the same subnet?
Considering you are trying to create 2 shared networks (irrelevant of their IP range), and I ASSUME you want them on the same VLAN? - then I don't think this alone is possible (2 network with the same VLAN) If you can do it, then it's easy to test what you are asking and have first hand-answer :) IN ACS workdl, in theory, 2 DHCP CAN operate in the same network, since ACS provisions explicit DHCP reservations for each IP - i.e. you can't just boot another VM (provisionined manually, outside ACS) in the same VLAN - as DHCP will reject to give it an IP. Best, On Wed, 2 Jun 2021 at 15:43, Yordan Kostov wrote: > Dear all, > > Is it possible to have one /24 network - for example > 10.10.10.0/24 where it is divided into 2 shared networks as follow: > > * Network A - 10.10.10.2-50 where 2 is Virtual router with DHCP for > the ip range mentioned > * Network B - 10.10.10.51-200 where 51 is Virtual router with DHCP for > the ip range mentioned > > I understand 2 DHCPs cannot operate in the same network but I was > wondering if this can be achieved somehow? > > Best regards, > Jordan > -- Andrija Panić
Re: [VOTE] Apache CloudStack 4.15.1.0 (RC1)
+1 (binding) On 6/2/21 11:50 AM, Rohit Yadav wrote: > Hi All, > > I've created a 4.15.1.0 release, with the following artifacts up for a vote: > > Git Branch and Commit SHA: > https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210602T1429 > Commit: aaac4b17099ba838a3f7b57400277ca9b23f98f5 > > Source release (checksums and signatures are available at the same > location): > https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/ > > PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884): > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > The vote will be open for 120 hours, until 7 June 2021. > > For sanity in tallying the vote, can PMC members please be sure to indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > For users convenience, the packages from this release candidate (RC1) and > 4.15.1 systemvmtemplates are available here: > https://download.cloudstack.org/testing/4.15.1.0-RC1/ > https://download.cloudstack.org/systemvm/4.15/ > > Documentation is not published yet, but the following may be referenced for > upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be > registered prior to upgrade) > https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade > > Regards. >
