Gabriel,
I'm happy to help review proposals if required.
-tim
On Wed, Dec 19, 2018 at 12:35 PM Gabriel Beims Bräscher <
gabrasc...@gmail.com> wrote:
> Hi Rafael,
>
> I am available to help, count on me!
> I have one question. Can anyone (one that is not a PMC/Committer) help to
> review present
I think there are three pieces in play. First there are guest OSes, second
the management server and third the hypervisors themselves. For the
hypervisors and management server I can see a more stringent set of
requirements. Going by the XenServer experience, legacy guests should
continue to work,
t; *Pierre-Luc DION*
> Architecte de Solution Cloud | Cloud Solutions Architect
> t 855.652.5683
>
> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Jan 12,
t; > >
> > >
> > >
> > > Can someone confirm if VRs receive management IPs in KVM deployments?
> > >
> > > On Fri, Jan 12, 2018 at 5:36 PM, Syed Ahmed
> wrote:
> > >
> > > > The reason why we used link local in the first
dom0 already has a DHCP server listening for requests on internal
management networks. I'd be wary trying to manage it from an external
service like cloudstack lest it get reset upon XenServer patch. This alone
makes me favor option #2. I also think option #2 simplifies network design
for users.
A
PLD,
One thing to add to your testing is template management. When I was doing
all the Packer stuff with XS 6.5 and 7, ACS needed to know if the template
was PV or HVM to provision properly. No idea if the ACS template logic has
changed since then, but something to be aware of.
>From a performanc
Syed,
I did a bunch of work on XenServer with Packer [1] before leaving Citrix.
My stuff works rather well and was tested with XS 6.2, 6.5 and 7. It
shouldn't be hard to validate with newest XS and updated Packer - I just
lack the infra to do the testing.
[1] https://github.com/xenserverarmy/pack
llo Sir,
>>
>> Can you please tell us more about the proposal to bring pure Xen in as
>> fully supported hypervisor and your project in security space?
>>
>> Regards,
>> TheAtom
>>
>> On Wed, Jul 6, 2016 at 4:15 PM, Tim Mackey wrote:
>>
>&
Jainesh, and by extension all members of TheAtom, welcome to the CloudStack
project. You'll want to join the development list (dev@cloudstack.apache.org),
and look at the contributing section here:
https://github.com/apache/cloudstack and here:
https://cloudstack.apache.org/developers.html.
A prop
Correct, all modern XenServer distros until 7 were centos 5.x. I doubt any
xapi changes would break cloudstack, but the plugins should be retested,
and btw it's also systemd time
On May 25, 2016 2:39 PM, "Remi Bergsma" wrote:
As far as I know previous versions were based on Centos 5 even ;-)
Reg
+1
When I went through this last time, not only was it hard to understand the
flows, but the XenServer version management was a pain. Would suggest
creating a base class which always works (i.e. is independent of XenServer
version) for core functions. Then add in that which exists for a specific
v
Prakash,
As you go through this, if you have questions related to how XenServer
works, do feel free to ask me. Another good avenue is the xs-devel list on
xenserver.org.
On Oct 27, 2015 6:27 PM, "Erik Weber" wrote:
> On Tue, Oct 27, 2015 at 10:34 PM, David Willard
> wrote:
>
> > Hi B. Prakash,
On Tue, Oct 20, 2015 at 7:08 PM, Eric wrote:
> Thanks, Erik!
> Is there a discussion forum where contributors can discuss documentation?
> I believe that, like all things in technology, there should be a set of
> conventions that guide authors in the use of common terms. e.g., Xen? Or
> Xen Proje
n is to add a
> > switch between both HA methods so one can choose which one suits best,
> and
> > for older XenServer versions we will restore the HA feature that way.
> >
> > Any thoughts?
> >
> > Regards,
> > Remi
> >
> > Op di 5 mei 2015 om 08:13
current 4.4+ behaviour (XenHA selects new pool master). When it is not, we
> do the CloudStack 4.3 behaviour where CloudStack is fully in control.
>
> I also talked to Tim Mackey and he wants to help implement this, but he
> doesn't have much time. The idea is to have so
s are removed, for a brief period (until new
> ipset entry replace the old one) old entries still persist. But since
> iptables rules are removed and no one is referencing them it is harmless.
> 2. In case of users upgrading, the old ipset data-structure is “iptreemap”
> or “iphash”, but
Rohit,
I just added a comment to update line 457 to tick-quote the vmchain as
you've done elsewhere. My main concern would be flushing the ipset while
the iptable entry still exists.
I am curious what in sm/util.py concerned you. That's all storage
management code and should have nothing to do
The most recent version of XCP is 1.6, and it approximately corresponds to
XenServer 6.1. XCP was effectively discontinued when XenServer 6.2 was
released in June 2013 (
http://www.xenproject.org/downloads/xen-cloud-platform-archives.html).
Importantly, there are no longer any patches being create
The ovs contained within XenServer 6.5 is capable of supporting VxLAN, but
as Adrian stated the control plane is missing. Prior XenServer versions
don't have an ovs capable of VxLAN. I *think* Contrail also supports
VxLAN, but I don't know what its status is wrt XenServer 6.5
-tim
On Wed, Apr 1
or 3rd party consumers such as CLI scripts, custom UI and
> possibly others.
>
> On Monday 02 February 2015 04:53 PM, Tim Mackey wrote:
>
>> Iirc, that was the only one.
>>
>> I don't agree with the reversion, but let me look at supporting both
>> once I get to
.
>
>
>
> Is there a list of all the API changes that have been made?
>
>
>
> Regards
>
>
>
> Geoff Higginbottom
>
>
>
> D: +44 20 3603 0542 <+442036030542> | S: +44 20 3603 0540 <+442036030540>
> | M: +447968161581
>
>
>
&g
Rohit, how does the issue manifest itself? I ask because I thought I'd
taken care of every scenario during upgrade.
On Feb 2, 2015 10:52 AM, "Rohit Yadav" wrote:
> Hi Tim,
>
> Geoff found a issue today that breaks backward compatibility for
> XenServer users.
>
> Until 4.4, XenServer traffic la
l.openvm.eu using virt-install+kickstarts (
> http://dl.openvm.eu/cloudstack/centos/ks/ ).
>
> HTH
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Tim Mackey"
Everyone,
I've been extending a XenServer builder some of the XenServer engineering
team have been working on to produce a VHD which would be suitable for
upload as a template. CentOS 7 is my guest OS type and have the XenServer
tools going in and guest password script running as a systemd servi
It's in master since September, and I think 4.5, but haven't explicitly
tried that.
On Dec 29, 2014 12:47 PM, "Pierre-Luc Dion" wrote:
> Hi Andrei,
>
> I haven't tested it but it might work with ACS 4.4. do you have a lab to
> validate this ? their is reference to XS6.5 into the code which is why
I've been working through a series of issues getting Ubuntu 12.04 LTS
templates to provision correctly, and I *think* most are really doc issues,
but before I run off and update docs I wanted to confirm that I'm doing the
right thing. Here's my list of issues, and what I did to get past my
"issue"
ill that cause any (potential) issue since you
> mentioned it has few bugs in it?
>
> Regards.
>
> > On 20-Nov-2014, at 10:23 pm, Tim Mackey wrote:
> >
> > It's the other way around. Newer XenServer works with older tools, not
> the
> > other way.
> > On N
lying
> Xen/XenServer hypervisor version is not 6.2?
>
> > On 20-Nov-2014, at 9:12 pm, Tim Mackey wrote:
> >
> > From the XenServer perspective, we have a small problem. The XenServer
> > tools are backward compatible, but not guaranteed forward compatible.
> What
&g
>From the XenServer perspective, we have a small problem. The XenServer
tools are backward compatible, but not guaranteed forward compatible. What
that means is we'd need to include the XenServer 5.6 tools, and those have
a commercial license. The XenServer 5.6 tools also have a few bugs which
w
Correct on both counts
On Mon, Oct 20, 2014 at 2:55 PM, Daan Hoogland
wrote:
> thanks Tim, from this I take that hypervisor versions are hardcoded still,
> and xenserver 6.5 is supported since 4.5. correct?
>
> On Mon, Oct 20, 2014 at 8:36 PM, Tim Mackey wrote:
>
> > Daan,
> Can you clarify that?
>
> Thanks!
>
> On Mon, Oct 20, 2014 at 11:29 AM, Daan Hoogland
> wrote:
>
> > Tim, these changes are needed? so 4.4.1 will not work with db changes...
> Do
> > you have a commit id?
> >
> > On Mon, Oct 20, 2014 at 6:54 PM, Tim Mackey w
I know that master had a bunch of cleanup work to make things work better
(commits were a month ago), but baring any significant issues, being able
to support a newer XenServer should be as simple as a database update. So
net of this master *today* should work fine with 6.5 (and the various
pre-re
> Hi Tim,
>
> No, we do not use XenServer HA.
>
> Remi
>
>
>
> On 7/25/14, 5:46 PM, "Tim Mackey" wrote:
>
> >Remi,
> >
> >Did you have the native XenServer HA enabled at the same time?
> >
> >-tim
> >On Jul 25, 2014 8:3
Remi,
Did you have the native XenServer HA enabled at the same time?
-tim
On Jul 25, 2014 8:31 AM, "Remi Bergsma" wrote:
> Hi guys,
>
> We had some serious corruption today, described in CLOUDSTACK-7184
> (XenServer specific).
> https://issues.apache.org/jira/browse/CLOUDSTACK-7184
>
> Some dis
Curious if XAPI being LGPL2 matters for this discussion.
http://www.xenproject.org/developers/teams/xapi.html
-tim
On Wed, Jul 16, 2014 at 9:28 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Doh! I mixed up master (4.5) with 4.4 in my e-mail. My mistake. I
> understand your questi
:50 PM, Hieu LE wrote:
>
>> Hi Tim and Mike,
>>
>>
>> On Tue, Jun 24, 2014 at 5:59 AM, Tim Mackey wrote:
>>
>>>This is an automatically generated e-mail. To reply, visit:
>>> https://reviews.apache.org/r/22799/
>>>
>>> On June
-
>
> (Updated June 20, 2014, 3:46 a.m.)
>
>
> Review request for cloudstack, Mike Tutkowski and Tim Mackey.
>
>
> Repository: cloudstack-git
>
>
> Description
> ---
>
> As discussed in mailing list, this patch is applied f
Mike,
I wouldn't expect things with the VMware Hypervisor (what they refer to
standalone ESXi) to work out of the box. Since you can't cluster things,
I'd expect only raw iSCSI to work, but it's been years since I've worked
with raw ESXi.
-tim
On Wed, Jun 18, 2014 at 11:40 AM, Mike Tutkowski <
I could easily have broken
something. If I've broken something, I probably won't be able to test
until next week due to travels. The question of xapi inclusion in distros
is one I'd need to check on.
> [1] http://www.xenproject.org/developers/teams/xapi.html
> [2] http:/
Rohit,
We've only supported xapi so far, so I'm curious if you had Xen Project 4.4
working before with xapi and if that is now broken. Nothing I did should
have impacted that, but it wasn't in my test suite so anything is possible
On Jun 17, 2014 11:21 AM, "Rohit Yadav" wrote:
> Hi,
>
> Xen Proj
Félicitations mon ami!
On Tue, Jun 10, 2014 at 1:46 PM, Ian Duffy wrote:
> Congrats Pierre-Luc!
>
>
> On 10 June 2014 17:07, Nguyen Anh Tu wrote:
>
> > Congratulation, Pierre-Luc!
> >
> > --Tuna
> >
> >
> > On Tue, Jun 10, 2014 at 10:34 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wr
Hieu,
I made a couple of minor edits to your design to ensure everything is
"XenServer" based. If you haven't done so already, please also fetch the
most recent master and base off of that. I refactored the old Xen plugin
into a XenServer specific one since Xen Project isn't currently supported,
On Mon, Jun 9, 2014 at 1:02 PM, Dave Scott wrote:
>
> > - It would be good to see a UI mock up for how users would configure
> > the Xen Project hypervisor option. I think that would go a long way
> > to helping with the mixed hypervisor cluster concept and how it could
> > be blocked.
>
> My co
Dave,
Thanks for putting this up on the wiki. A few things jumped out at me...
- Please change "Xen" to "XenProject" or "Xen Project" as appropriate.
There's already a ton of confusion out there, and I'd like to see us
get our terms correct from the outset where ever possible.
- It would be good
If you can give me the commit ID for your HEAD, I'll check and see
what's up. It could be another conflict needing resolution.
-tim
On Fri, Jun 6, 2014 at 12:16 PM, sebgoa wrote:
>
> On Jun 6, 2014, at 5:17 PM, Tim Mackey wrote:
>
>> Dave,
>>
>> I've
Dave,
I've submitted a merge review request
(https://reviews.apache.org/r/22270/) yesterday. If you want to avoid
having to potentially deal with a bunch of conflicts, you might want
to see if your patches apply cleanly there and let me know. Happy to
help with any conflict resolution.
btw, I d
Hieu,
If I understand the objective correctly, you are trying to reduce the
IO associated with a desktop "start of day" boot storm. In your
proposal, you're effectively wanting to move the CloudStack secondary
storage concept to include a locally attached storage device which is
SSD based. While
I've just submitted a review request which is essentially a merge of
the xen2server feature branch back into master. Since this is a
refactoring of the Xen plugin to make it more explicitly a XenServer
plugin per the feature:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Convert+Xen+usage
can help.
>
>
> ---
> Thanks,
> Yitao
> jiangyt.github.io
>
>
> On Thu, Apr 24, 2014 at 7:22 AM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
>
> > Where is this HYPERVISOR_VERSION? In the code? Docs?
> >
> > From: Tim
I'm running through some bugs with my Xen->XenServer work and just ran
across the HYPERVISOR_VERSION being the Xen version and not the XenServer
version. Does anyone know why that is? Given that feature/function in
XenServer is tied to the XenServer version, I see using the Xen version as
a bug w
his change, for example
> because of changes in some parsing code.
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Tim Mackey [mailto:tmac...@gmail.com]
> Sent: 16 April 2014 01:31
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS4.5] move from
en Turner
> >
> >
> > -----Original Message-
> > From: Sebastien Goasguen [mailto:run...@gmail.com]
> > Sent: 15 April 2014 08:36
> > To: dev@cloudstack.apache.org
> > Subject: [ACS4.5] move from xen 2 xenserver
> >
> > Folks,
> >
> &g
Tracy,
XCP itself was made EOL last year in favor of XenServer. You can of course
still continue to use XCP 1.6, but there will be no future releases and
development is now XenServer based. If the dom0 distro matters, you should
take a look at the xenserver-core work going on.
-tim
On Fri, Apr
Historically CloudStack has used Xen and XenServer interchangeably to refer
to any XenAPI based implementation. With the recent release of Xen Project
4.4 (http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/), and
interest in alternate architectures like ARM, the loose definition of our
Xen
Hi everyone,
I'm updating my deck on hypervisor differences for 4.3, and I'd like
confirmation of what I understand made the cut. Feedback welcome.
- Hyper-V 2012 R2 added (Donal, I'll be hitting you up to confirm all the
HV stuff)
- vSphere 5.5 added and supporting identical features to vSphere
How deep into dependencies would this go? For example, if a new router VM
was required would that also be checked?
A chunk of the race conditions and state change issues should be resolvable
with ticket reservation system logic, but I'd be concerned the required
locks could create problems during
e:
> Great - thanks!
>
> I was just trying to make sense of the numbers. :)
>
>
> On Thu, Jan 30, 2014 at 4:36 PM, Tim Mackey wrote:
>
> > I'll need to confirm with engineering, but that makes sense. I'll also
> see
> > if there is a different format spec
; devserial: scsi-36f47acc133793877007e
> blobs ( RO):
> local-cache-enabled ( RO): false
> tags (SRW):
>
>
> On Thu, Jan 30, 2014 at 4:08 PM, Tim Mackey wrote:
>
> > I'm assuming that's the value fr
I'm assuming that's the value from XenCenter. What does the cli say? I
could see this being just a formatting question.
On Jan 30, 2014 5:59 PM, "Mike Tutkowski"
wrote:
> Hi,
>
> Does anyone know how a XenServer SR could (correctly) say more space is
> being used than is allocated?
>
> This is wh
Mike, you might want to post this to xs-devel on XenServer.org. Some of
the storage engineers there would be in s better position to diagnose.
On Dec 19, 2013 5:10 PM, "Mike Tutkowski"
wrote:
> Hi,
>
> I have been experimenting with VM snapshots on XenServer and have noticed a
> problem that I h
#x27;s IP address and 3260 is
> the port) that I can create SRs using different CHAP credentials.
>
> Can anyone think of a "got-cha" here?
>
> Thanks!
>
>
> On Wed, Dec 18, 2013 at 3:18 PM, Tim Mackey wrote:
>
> > Mike,
> >
> > I'm re
argets.
>
> Do you know of a way to delete those cached CHAP credentials via XAPI so
> when new ones are used for discovery they can work?
>
> Thanks!
>
>
> On Wed, Dec 18, 2013 at 2:22 PM, Tim Mackey wrote:
>
> > Unfortunately what you're experiencing is how
Unfortunately what you're experiencing is how it works. While XenServer
does support different CHAP credentials by SR, it only supports a single
CHAP credential for discovery. It can be made to work, but you'd need to
either modify how the storage manager works to pull it off, or rewrite some
of
Good evening everyone. I'm presenting at Collab this week on hypervisor
selection in CloudStack. While I've been running CloudStack since the
pre-Apache days, my experience is obviously limited to what I've personally
implemented. Since I want to keep this session factual and avoid any bias,
I'm
64 matches
Mail list logo
