On Mon, Jun 04, 2018 at 02:40:09PM -0500, Sean McGinnis wrote:
> >
> > Our CI has been chugging along since June 2nd (not really related to
> > the timing of your e-mail, it just so happened that we fixed another
> > small problem there). You can see the logs at
> >
> > http://logs.ci-openstac
On Sat, Jun 02, 2018 at 06:13:23PM -0500, Jay S Bryant wrote:
> All,
>
> This note is to make everyone aware that I have submitted patches for a
> number of drivers that have not run 3rd party CI in 60 or more days. The
> following is a list of the drivers, how long since their CI last ran and
>
On Fri, Mar 16, 2018 at 09:39:14AM -0700, Dan Smith wrote:
> > Can you be more specific about what is limiting you when you use
> > volume-backed instances?
>
> Presumably it's because you're taking a trip over iscsi instead of using
> the native attachment mechanism for the technology that you're
On Fri, Mar 16, 2018 at 09:23:11AM -0700, melanie witt wrote:
> On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote:
> > Would there be any major opposition to adding a StorPool shared
> > storage image backend, so that our customers are not limited to
> > volume-backed
tances.
> On Fri, Mar 16, 2018 at 05:33:30PM +0200, Peter Penchev wrote:
> > Hi,
> >
> > A couple of years ago I created a Nova spec for the StorPool image
> > backend: https://review.openstack.org/#/c/137830/ There was some
> > discussion, but then our company co
Hi,
A couple of years ago I created a Nova spec for the StorPool image
backend: https://review.openstack.org/#/c/137830/ There was some
discussion, but then our company could not immediately allocate the
resources to write the driver itself, so the spec languished and was
eventually abandoned.
N
We have just restored and submitted new patchsets for the StorPool
block storage driver in the three components:
- os-brick: https://review.openstack.org/#/c/192639/
- cinder: https://review.openstack.org/#/c/220155/
- nova: https://review.openstack.org/#/c/140733/
Now, while we do realize that th
On Fri, Aug 28, 2015 at 6:29 PM, Peter Penchev
wrote:
> On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev
> wrote:
>> On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote:
>>> Hi Peter,
>>>
>>> Your log files require downloads. Please fix it such that they c
On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev
wrote:
> On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote:
>> Hi Peter,
>>
>> Your log files require downloads. Please fix it such that they can be viewed
>> directly [1]
>
> Hi, and thanks for the fast re
On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote:
> Hi Peter,
>
> Your log files require downloads. Please fix it such that they can be viewed
> directly [1]
Hi, and thanks for the fast reply! Yes, I'll try to change the
webserver's configuration, although the snippet in the FAQ won''t hel
Hi,
Some time ago I sent
http://lists.openstack.org/pipermail/third-party-announce/2015-August/000261.html
to the third-party-announce list as a reply to a message about the
StorPool Cinder third-party CI being disabled. Well, as I wrote in my
reply there, I think that we have done what Mike Pere
real objections to the spec, it was
even approved back then, but the actual code did not get enough
approval votes.
So, yeah, sorry again for posting to the whole list... and thanks
in advance for your time! :)
G'luck,
Peter
--
Peter Penchev r...@ringlet.net r...@freebsd.org p...@s
Hi,
There are a couple of Tempest volume tests, like
test_rescued_vm_detach_volume or test_list_get_volume_attachments,
that either sometimes[0] or always attempt to detach a volume from a
running instance while the instance could still be keeping it open.
Unfortunately, this is not completely com
Hi,
During the Juno and Kilo timeframes, there was an idea to use libvirt
storage pools for the Nova image backends. I believe that the plan
back then was to deprecate image backend drivers that do not use
libvirt storage pools in Kilo and them remove them altogether in
Liberty. Is this still th
On Tue, Feb 10, 2015 at 12:34 PM, Daniel P. Berrange
wrote:
> On Tue, Feb 10, 2015 at 12:28:27PM +0200, Peter Penchev wrote:
>> Hi,
>>
>> I'd like to request a feature freeze exception for the change:
>> https://review.openstack.org/140733/
>>
>
Hi,
I'd like to request a feature freeze exception for the change:
https://review.openstack.org/140733/
It's a small, self-contained driver for attaching StorPool-backed
Cinder volumes to existing Nova virtual machines. It does not touch
anything outside its own bailiwick (adds a new class to
Hi,
I'd like to request an exception for Add the StorPool volume
attach/detach proposal.
https://review.openstack.org/#/c/115716/
This is a very simple driver that allows Nova virtual machines to use
StorPool distributed volumes (already created in Cinder) as additional
disks. All that the drive
On Mon, Dec 1, 2014 at 9:52 PM, Solly Ross wrote:
> Hi Peter,
>
>> Right. So just one more question now - seeing as the plan is to
>> deprecate non-libvirt-pool drivers in Kilo and then drop them entirely
>> in L, would it still make sense for me to submit a spec today for a
>> driver that would
Hi,
Hm, looks like I was a bit confused as to the procedure of submitting
a blueprint and a spec for a new Glance image backend driver - and
yeah, the actual text of the "Reviewers" section of the spec should
have made me at least ask on the list... So here I am, asking, and
sorry for the prematu
On Wed, Nov 26, 2014 at 10:26 PM, Solly Ross wrote:
> Hi!
>>
>> Some days ago, a bunch of Nova specs were approved for Kilo. Among them was
>> https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools
>>
>> Now, while I do recognize the wisdom of using storage pools, I do see a
>> coup
Hi,
Some days ago, a bunch of Nova specs were approved for Kilo. Among them
was https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools
Now, while I do recognize the wisdom of using storage pools, I do see a
couple of possible problems with this, especially in the light of my
upcom
21 matches
Mail list logo
