fuel-dev team mailing list archive

[Andrew Woodward <xarses@xxxxxxxxx>]

I think this raises some feature gaps we have.
1) We need to provide the packages with the repos on the ISO.
2) We should add a field for "install additional packages" in cluster
settings (maybe instead just do #3, but it would be awesome to have
both)
3) We should add a post provision and post deployment scripts (kinda
cloud init style) so that users can customize their nodes more
efficiently.

On Mon, Jun 9, 2014 at 12:49 PM, Roman Alekseenkov
<ralekseenkov@xxxxxxxxxxxx> wrote:
> It's not about installation time. If we don't put tcpdump on OpenStack
> nodes, that makes it hard to debug issues in the field. We should have it
> built-in.
>
> It's only 1Mb, so the impact on installation time should be minimal.
> Especially given that all compute nodes are provisioned in parallel.
>
> Thanks,
> Roman
>
>
> On Sun, Jun 8, 2014 at 2:14 PM, Andrey Danin <adanin@xxxxxxxxxxxx> wrote:
>>
>> I don't think it's a good idea to manipulate with our base repos on a
>> Master node. Let's develop a standard way to create supplemental
>> repositories and provide them to target nodes. For instance, there should be
>> MCollective/Astute calls to list/create/update additional DEB/RPM repos on a
>> Master node and add/remove them on Target nodes. In this case we will be
>> able to easily plug in such features as VMWare NSX which requires
>> proprietary packages be obtained and installed on the fly.
>>
>>
>> On Sat, Jun 7, 2014 at 12:24 PM, Matthew Mosesohn <mmosesohn@xxxxxxxxxxxx>
>> wrote:
>>>
>>> Mike, Aleksandr,
>>>
>>> Not installing by default keeps install time down, and doing a turnkey
>>> "enable diagnostic mode" command on Fuel Master ought to be trivial.
>>> I've got a plan already in mind. I'll check out what's already
>>> available for us and submit a patchset on Monday.
>>>
>>> Ubuntu repository building is actually quite a challenge. What's
>>> easier is to offer a supplemental repository, managed by reprepro.
>>> I've wanted to get this feature into Fuel for a long time already and
>>> we have the package on our build mirrors, but it's not included in the
>>> ISO. The reason why it's hard to update the main repository is there's
>>> a lot of metadata packed into the base repo that is quite difficult to
>>> regenerate using standard APT tools. We got lucky with using Ubuntu to
>>> build the ISO because all the YUM tools are available for building
>>> CentOS repos, but vice versa is quite limited (CentOS creating Ubuntu
>>> repos). The most logical solution, of course, is to use an Ubuntu
>>> Docker container for repo management. We could easily do it, but it
>>> will add a bit more size to the base Fuel ISO. Let me know which route
>>> sounds worth pursuing.
>>>
>>> Best Regards,
>>> Matthew Mosesohn
>>>
>>> On Sat, Jun 7, 2014 at 10:25 AM, Aleksandr Dobdin
>>> <sanek.dobdin@xxxxxxxxx> wrote:
>>> > Mike,
>>> >
>>> > Yes, it requires less 2 minutes to provisioning of each node and we can
>>> > install them manually, but
>>> > 1) These packages should be stored in the repositories on master node
>>> > (some
>>> > customers don't have the Internet access on cloud)
>>> > Also, we need to rebuild repository if we add packages to repository.
>>> > Any
>>> > suggestions how to rebuild Ubuntu-repository on master-node?
>>> > 2) Public repositories are disabled by default and we need to add it
>>> > manually.
>>> >
>>> > Thanks,
>>> > Aleksandr Dobdin
>>> >
>>> >
>>> > 2014-06-07 4:32 GMT+04:00 Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>:
>>> >
>>> >> How much time does it take to install those packages? This is the only
>>> >> thing I'm care about. If it adds 2 minutes to provisioning of each
>>> >> node,
>>> >> then I would say you can install them by yourself when you need them,
>>> >> unless
>>> >> you have a serious reason to have those packages available on the
>>> >> node.
>>> >> Obviously, they should be available on the master node.
>>> >>
>>> >> Thanks,
>>> >>
>>> >>
>>> >> On Wed, Jun 4, 2014 at 10:38 PM, Roman Alekseenkov
>>> >> <ralekseenkov@xxxxxxxxxxxx> wrote:
>>> >>>
>>> >>> We also need this on target nodes provisioned by Fuel
>>> >>>
>>> >>> Roman
>>> >>>
>>> >>>
>>> >>> On Wed, Jun 4, 2014 at 10:36 PM, Matthew Mosesohn
>>> >>> <mmosesohn@xxxxxxxxxxxx> wrote:
>>> >>>>
>>> >>>> Hi Aleksandr,
>>> >>>>
>>> >>>> This topic came up yesterday in some other discussion. I believe we
>>> >>>> could extend dockerctl to install this on Fuel Master and all of its
>>> >>>> docker containers by running dockerctl diagtools. Can you please add
>>> >>>> it to your blueprint? I will work on it as soon as the packages are
>>> >>>> available.
>>> >>>>
>>> >>>> Additionally, can you create a spec in
>>> >>>> https://github.com/stackforge/fuel-specs that matches the example
>>> >>>> spec?
>>> >>>>
>>> >>>> On Thu, Jun 5, 2014 at 9:22 AM, Aleksandr Dobdin
>>> >>>> <sanek.dobdin@xxxxxxxxx> wrote:
>>> >>>> > I've created a blueprint which contains list of some packages.
>>> >>>> >
>>> >>>> >
>>> >>>> > https://blueprints.launchpad.net/fuel/+spec/fuel-additional-packages
>>> >>>> >
>>> >>>> > The following packages are important to monitor/debug issues on
>>> >>>> > cloud:
>>> >>>> > nmap, tcptraceroute, iperf, tcpdump, pssh, tmux (can create a
>>> >>>> > session
>>> >>>> > from
>>> >>>> > command line/scripts)
>>> >>>> >
>>> >>>> > Packages might be installed on fuel-node, controllers, computes.
>>> >>>> >
>>> >>>> > Thanks in advance.
>>> >>>> >
>>> >>>> >
>>> >>>> > --
>>> >>>> > Mailing list: https://launchpad.net/~fuel-dev
>>> >>>> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> >>>> > Unsubscribe : https://launchpad.net/~fuel-dev
>>> >>>> > More help   : https://help.launchpad.net/ListHelp
>>> >>>> >
>>> >>>>
>>> >>>> --
>>> >>>> Mailing list: https://launchpad.net/~fuel-dev
>>> >>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> >>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> >>>> More help   : https://help.launchpad.net/ListHelp
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Mailing list: https://launchpad.net/~fuel-dev
>>> >>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> >>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> >>> More help   : https://help.launchpad.net/ListHelp
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Mike Scherbakov
>>> >> #mihgen
>>> >>
>>> >>
>>> >> --
>>> >> Mailing list: https://launchpad.net/~fuel-dev
>>> >> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> >> Unsubscribe : https://launchpad.net/~fuel-dev
>>> >> More help   : https://help.launchpad.net/ListHelp
>>> >>
>>> >
>>> >
>>> > --
>>> > Mailing list: https://launchpad.net/~fuel-dev
>>> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> > Unsubscribe : https://launchpad.net/~fuel-dev
>>> > More help   : https://help.launchpad.net/ListHelp
>>> >
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>> --
>> Andrey Danin
>> adanin@xxxxxxxxxxxx
>> skype: gcon.monolake
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Andrew
Mirantis
Ceph community