--- I ever used ---
1) CyberDuck
2) Owncloud (What's the problem in your test?)
3) Gladinet client
4) SwiftStack Web Console
5) Most of AWS S3 client tools, but you need to enable Swift3 middleware
support
6) OpenStack DashBoard
7) Maldivica gateway
-- I never use but should work --
8) SME
Hope
Hi stackers,
I am running devstack with heat enabled.
I was trying to create a new stack using WordPress_With_LB.template from github.
However, it failed and I got the following error in screen-h-eng.log
2013-07-05 10:00:13.998 26996 INFO heat.engine.resource [-] Validating
LoadBalancer "LoadBal
On Thu, Jul 4, 2013 at 6:16 PM, pablo fernandez
wrote:
> Leandro, Brano,
I wrote the previous mail in a hurry.. I hope this one might clarify it a bit
1) DFM dataset metadata
Folsom driver is using DFM to store Project id (tenant) together with
the volume. Essex driver did not do that, so his v
Cool, thanks one more time Lean and Brano, you guys rock.
On Thu, Jul 4, 2013 at 2:26 PM, Leandro Reox wrote:
> Yep thats right pablo !
>
>
> On Thu, Jul 4, 2013 at 2:02 PM, pablo fernandez <
> fernandezpabl...@gmail.com> wrote:
>
>> Guys,
>>
>> I also found that the blocking_device_mapping tab
Yep thats right pablo !
On Thu, Jul 4, 2013 at 2:02 PM, pablo fernandez
wrote:
> Guys,
>
> I also found that the blocking_device_mapping table only contains entries
> for the volumes that are "in-use".
>
> Since we're planning a less transparent cloud migration, with detached
> volumes seems I d
Hi people,
I want to use my Swift all in One with a graphical client, to put /
retrieve objects. i heard that we can use Cyberduck (but there is problem
of port) or Owncloud as Swift client but didn't find good references.
If any person could help me or suggest other clients, it would be really
g
Guys,
I also found that the blocking_device_mapping table only contains entries
for the volumes that are "in-use".
Since we're planning a less transparent cloud migration, with detached
volumes seems I don't have to copy this information. The only change needed
is to copy the volumes_* info and p
Leandro, Brano,
I'm effectively migrating only the openstack installation, the DFM remains
the same. However, if I read Brano's email correctly, besides migrating the
information on openstack DB I also have to change metadata that DFM, is
that right?
Here's an example of a volume I have on Essex
Pablo,
On folsom the block_device_mappings table its on novadb too, i totally miss
the Brano's recommendation of uuid conversion and metadata, asumming that
you hit the same dfm.
We had to do that a couple of times, but generally as all our vms are
stateless, we create them on the "new" cloud, and
On Wed, Jul 3, 2013 at 11:24 PM, pablo fernandez
wrote:
> Hi list!
>
> Any advice on this? Has somebody already tried it (and hopefully succeeded).
We did this migration "in-place". On day D, we dumped Essex
Openstack/DFM DB and restored in Folsom. I have created a patch for
Folsom Netapp driver
Hey Lean,
Thanks a ton, I would have totally missed the block_device_mapping table
(because on Folsom it lives on the nova db, not cinder's).
Seems you guys already did this stuff? or something similar?
Pablo
On Thu, Jul 4, 2013 at 9:57 AM, Leandro Reox wrote:
> Pablo,
>
> All the logic for
Pablo,
All the logic for device mappings its on the database, so be sure to
replicate (carefull no to overlap volumes id) all your volume data from the
table :
- volumes
- volumes metadata
An the most important one:
- block_device_mappings
On this tables is where actually resides the conection
Hi list!
I'm working on a company that has 2 openstack clouds, an essex installation
and a folsom one. I'm trying to migrate a netApp volume from one to the
other, checking the required fields in the database to copy the metadata.
Obviously both volumes would be detached.
Any advice on this? Has
On Mon, Jul 1, 2013 at 9:02 AM, Robert van Leeuwen
wrote:
>> I would like to thank the XFS folks at Redhat for letting us know about the
>> improvements in XFS,
>> and the XFS team in general for the great work they have done.
> Thanks for the heads up.
> Do you, or any of the Redhat people, kno
Hi!
I am very sorry for the late answer - I was really busy last week. Going
back to this topic, answering inline:
On 2013/26/06 23:05, Monty Taylor wrote:
Hi!
Thanks for looking in to Phabricator for us! The feedback is helpful. I
think we've also got some concerns around elements of it as
Hi,
I am not a Neutron expert, but what I learned, is that it has a very
flexible architecture.
With XenServer, your compute openvswitch is in dom0, so you need to get
an agent to controll that, to create the ports for you. The issue is,
that your OpenStack VM is not the same as dom0. One option
On Wed, Jul 3, 2013 at 8:47 AM, Li, Leon wrote:
> However a scale-out NAS could also have these benefits, if you build the
> scale-out NAS with open source cluster FS(for example HDFS), just like many
> Internet company did.
Please feel free to considerate contributing to this blueprint effort :
17 matches
Mail list logo
