Hi,

Yes, I didn't reviewed all the features of cinder since it's just recently installed. I'm using it for serving LVM volumes from different machines. Works great.

But I cannot install anything on this NAS, and therefore it has not cinder support. Just plain iscsi support. Even the tgt manager cannot be modified.

Maybe I can find a way. But not just now. And manufacture will not support it, since it's very lowend. And as they said "There are too many fishes on this sea".

Thank you for the advise.

El 11/12/13 02:29, 郭龙仓 escribió:
Have you tried Cinder ? Cinder is responsible for volume management. You can configure your NAS as Cinder's back-end storage, then create and attach Cinder Volumes as disks to your Instances.



2013/12/11 Matt Kassawara <mkassaw...@gmail.com <mailto:mkassaw...@gmail.com>>

    This document was helpful for me...

    http://openstack.redhat.com/Networking_in_too_much_detail


    On Tue, Dec 10, 2013 at 12:36 PM, Gonzalo Aguilar Delgado
    <gagui...@aguilardelgado.com <mailto:gagui...@aguilardelgado.com>>
    wrote:

        Hi Scott

        I have OVS. I did took a look to this document some time ago,
        the problem is that right now there is a mess in documention
        and you really don't know what's current and what's obsolete.

        I will take a look again and post if any doubts.

        Thank you for the reference.




        El 10/12/13 18:47, Scott Devoid escribió:
        Which driver are you using?

        For OVS and Linux Bridge, there was decent documentation
        (including diagrams) in the Grizzly-era Networking
        Administration Guide, the "Under the Hood" section:
        
http://docs.openstack.org/grizzly/openstack-network/admin/content/under_the_hood_openvswitch.html

        That guide is missing from the Havana release and from trunk.
        It seems to be replaced by a unified "Cloud Administration
        Guide" but the networking section in there is missing
        anything that resembles this section.


        On Tue, Dec 10, 2013 at 11:08 AM, Gangur, Hrushikesh (R & D
        HP Cloud) <hrushikesh.gan...@hp.com
        <mailto:hrushikesh.gan...@hp.com>> wrote:

            
http://techbackground.blogspot.com/2013/05/debugging-quantum-dhcp-and-open-vswitch.html


            -----Original Message-----
            From: Gonzalo Aguilar Delgado
            [mailto:gagui...@aguilardelgado.com
            <mailto:gagui...@aguilardelgado.com>]
            Sent: Tuesday, December 10, 2013 3:35 AM
            To: openstack@lists.openstack.org
            <mailto:openstack@lists.openstack.org>
            Subject: [Openstack] OpenStack networking and disks...

            Hi,

            Is there any document that explains inner workings of
            neutron networking?

            I have an internal NAS that does not have support for
            openstack, and until we have resources to replace I want
            to use it to server iscsi disks.

            I can create disks by hand and associate to instances.
            But first I have to configure how will it connect to the
            network.


            For now it's serving disks on a network that's accessible
            to the
            floating ip network. That's not the best way but I cannot
            change it
            because other instances that are not part of the
            openstack network are
            using it. For example maas server.

            So I can add it another ip for each private network so it
            can serve
            disks on the private/management net. But how do I
            configure virtual
            routers so this NAS is accessible from private range (for ex.
            192.168.10.0/24 <http://192.168.10.0/24>).

            Is this the best way to do it?

            What's the best way to add servers that are not part of
            the openstack
            deployment to the net, for example a nagios monitoring
            set for each
            tenant so they have monitoring of their instances but
            they have not to
            install.

            Best regards,

            _______________________________________________
            Mailing list:
            http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
            Post to     : openstack@lists.openstack.org
            <mailto:openstack@lists.openstack.org>
            Unsubscribe :
            http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

            _______________________________________________
            Mailing list:
            http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
            Post to     : openstack@lists.openstack.org
            <mailto:openstack@lists.openstack.org>
            Unsubscribe :
            http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




        _______________________________________________
        Mailing list:
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
        Post to     : openstack@lists.openstack.org
        <mailto:openstack@lists.openstack.org>
        Unsubscribe :
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



    _______________________________________________
    Mailing list:
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
    Post to     : openstack@lists.openstack.org
    <mailto:openstack@lists.openstack.org>
    Unsubscribe :
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to