Managing base and other snappy apps

[Manik Taneja]

On Tue, Jul 28, 2015 at 3:01 PM, Eystein Måløy Stenberg <
eystein.stenberg at gmail.com> wrote:

> Thanks!
>
> I see webdm has references to "snappy's packages api", e.g. in
> webdm/snappy/handlers.go it says
>
> // MakeMuxer sets up the handlers multiplexing to handle requests against
> snappy's
> // packages api
> func (h *Handler) MakeMuxer(prefix string) http.Handler {
> ..
>
> Is this API something that is part of a base installation of snappy or
> webdm itself? Is it intended to be used by other snaps than webdm, and if
> so, is it documented?
>
Ricardo, can you please advice. AIUI, this is part of the webdm
infrastructure and interacting with the store backend hosted by Canonical

The reason I'm asking is that I'm wondering what I should build my
> framework snap on top of for doing package operations.
> I have no problems using the snappy CLI, but I just wanted to check if
> there is a "more official" (e.g. http API) method first.
>
> We are working on providing REST APIs to manage the device. That will be a
cleaner way to achieve this..

>
> I'm not well-versed in go, so sorry for not being able to deduce this
> myself. :-/
>
>
>
> On Tue, Jul 28, 2015 at 1:16 PM, Manik Taneja <manik.taneja at canonical.com>
> wrote:
>
>>
>>
>> On Tue, Jul 28, 2015 at 12:51 PM, Eystein Måløy Stenberg <
>> eystein.stenberg at gmail.com> wrote:
>>
>>> Thanks for the answers everyone!
>>> I will play a bit more given your input.
>>>
>>> webdm seems similar to what I had in mind, is the source code for it
>>> available somewhere?
>>>
>> $ sudo add-apt-repository ppa:snappy-dev/tools
>> $ sudo apt-get update
>> $ sudo apt-get upgrade
>> $ sudo apt-get install snappy-tools bzr
>>
>> $ bzr branch lp:webdm
>>
>>
>>
>>> I'm in particular curious about the required security policies (I see
>>> it's a framework, not an app) and interaction with the snappy CLI manager
>>> (if that what it's using).
>>>
>> yes, you will need to work with Canonical to define custom security
>> policies for your framework
>>
>>>
>>>
>>>
>>> On Tue, Jul 28, 2015 at 9:54 AM, Charles Butler <chuck at dasroot.net>
>>> wrote:
>>>
>>>> As a side note the webdm snap exists as a front end to snaps for snappy
>>>> and managing them.
>>>>
>>>> It's a great resource for you to model after for your own front end.
>>>> Hope this helps, I'm pretty fresh on my voyage with snappy my self.
>>>>
>>>> If you need additional help I know the fine people in #snappy on
>>>> freenode are a great complimentary companion to this mailing list.
>>>>
>>>> All the best,
>>>> On Jul 23, 2015 10:21 PM, "Eystein Måløy Stenberg" <
>>>> eystein.stenberg at gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am new to Snappy, but have read much of the docs and tried it for a
>>>>> few hours.
>>>>> No problems and it looks simple so far, but I had a few questions
>>>>> about managing snaps.
>>>>>
>>>>> On [1] I get a feeling for how the base system itself is updated. But
>>>>> is this entirely managed with the "ubuntu-core" snap? So if I run "snappy
>>>>> update ubuntu-core" it will download a new image (if any) to the passive
>>>>> partition? Or are there other snaps that should be updated as part of the
>>>>> base system as well (I see "generic-amd64" which sounds like a base snap).
>>>>> Any other software that comprises a base system update?
>>>>>
>>>>> Furthermore, assuming base system update goes well, I should reboot to
>>>>> the other partition. Is there a preferred method do this (I see a
>>>>> --automatic-reboot option to snappy update) or will the regular "shutdown
>>>>> -r now" do the job well enough?
>>>>>
>>>>> Is there a way to see which snaps can be updated? I am looking for
>>>>> something similar to "apt-get -s upgrade". Or would this be the difference
>>>>> in version between "snappy list -v" and "snappy search"?
>>>>>
>>>>> Finally, is there a way for software to manage snaps, just like you
>>>>> can being logged in as superuser with the "snappy" command? I am planning
>>>>> to make an application that can update and manage snaps. Supposedly it
>>>>> would either need to be part of the base OS (which I guess is unlikely it
>>>>> would be allowed to) or it would have to be packaged as a snap with special
>>>>> privileges (perhaps as a framework)?
>>>>>
>>>>> Thanks for reading to the end and appreciate any help! :)
>>>>>
>>>>> [1]
>>>>> https://developer.ubuntu.com/en/snappy/guides/transactional-updates/
>>>>>
>>>>> --
>>>>>
>>>>> Eystein Stenberg
>>>>>
>>>>> --
>>>>> snappy-devel mailing list
>>>>> snappy-devel at lists.ubuntu.com
>>>>> Modify settings or unsubscribe at:
>>>>> https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>>>>>
>>>>>
>>>
>>> --
>>> snappy-devel mailing list
>>> snappy-devel at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>>>
>>>
>>
>
> --
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150728/a2a5c06b/attachment-0001.html>