Thanks, Jayapal!
> On Jul 26, 2017, at 11:22 PM, Jayapal Uradi
> wrote:
>
> Hi Mike,
>
> Long back I got issue related to mysql-connector. I followed the below steps,
> see if this helps for installing mysql-connector.
>
> #mysql-connector-python
>
Catch same issue. I'm using virtualenv and here is my requirements.txt:
https://dev.mysql.com/get/Downloads/Connector-Python/mysql-connector-python-2.1.6.tar.gz
Marvin
nose-timer
working fine.
On 27/07/17 05:16, Tutkowski, Mike wrote:
Hi everyone,
I am having trouble installing Marvin on
> Op 27 juli 2017 om 17:13 schreef Syed Ahmed :
>
>
> I would start by adding a comment to the open PRs to see if the author is
> responsive. If that's the case, then it means that review is need and we
> can add the "waiting-for-review" tag. There are a few PRs that are in
Hi All,
I am planning to add 4 new parameters to the disk offering. The use case
for this is as follows:
We want to provide a provisioned IOPS style offering to our customers with
managed storage like SolidFire. The model is similar to GCE where we have
IOPS scale with the size based on a
I would start by adding a comment to the open PRs to see if the author is
responsive. If that's the case, then it means that review is need and we
can add the "waiting-for-review" tag. There are a few PRs that are in that
state but there are far more out there which need to have this tag added.
-1 on Arch as well. Moving to Debian 9 seems the wiser choice IMO. I've
used Packer before and I really like it, the only downside that I see is
that Packer lacks support for XenServer VHD images. There is some work on a
XenServer plugin but I haven't tested that. If the community decides to use
I think we had a little bit of discussion around this at CCC. Config drive
really does solve a lot of problems with existing implementation of using
the Cloudstack Metadata provider for cloud-init. Overall it is a much
superior solution as pointed by Wido. However, we don't want to completely
Thanks, Dmytro!
> On Jul 27, 2017, at 5:18 AM, Dmytro Shevchenko
> wrote:
>
> Catch same issue. I'm using virtualenv and here is my requirements.txt:
>
> https://dev.mysql.com/get/Downloads/Connector-Python/mysql-connector-python-2.1.6.tar.gz
> Marvin
>
That sounds good, Syed.
On Jul 27, 2017, at 2:14 PM, Syed Ahmed
> wrote:
Mike, you are absolutely right. I have added 4 new fields in the disk_offering
table. The driver code won't need to change as I would pass the min and max
IOPS after
Hi Syed,
I have a couple questions.
What about the minimum number of IOPS a storage provider can support?
For example, with SolidFire, in some releases we can go down as low as 100 IOPS
per volume and in newer releases as low as 50 IOPS per volume.
Perhaps you should just leave it to the
So then, based on the use case you mentioned, you are saying you don't really
care about minimum limits, right?
Are the values you specify for the disk offering going to be translated into
the standard min and max values that get stored in the volumes table? If that
is the case, then the
That's a good idea to use labels to tag PRs. Does it make sense to add an
explicit label such as 'closeable' or something more appropriate on PRs that
are not getting any traction either from reviewers or from the author
themselves?
For the 4.9.3.0 effort, I'm trying to go through several PRs
Hi Mike,
In case of min and max values of IOPS for a specific offering, there is
another use case. We want to offer tiered storage. Right now if we have a
disk offering, there is no way for us to limit the IOPS that the customer
can set. We want to have say an offering which scales upto 10k IOPS
Mike, you are absolutely right. I have added 4 new fields in the
disk_offering table. The driver code won't need to change as I would pass
the min and max IOPS after translating them. I am not using a fifth
parameter since it is an either or situation, if you pass IOPS/GB in your
API call and also
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]
15 matches
Mail list logo