Canonical Voices

Posts tagged with 'uncategorized'

Michael

Just documenting for later (and for a friend and colleague who needs it now) – my notes for setting up openstack swift using juju. I need to go back and check whether keystone is required – I initially had issue with the test auth so switched to keystone.

First, create the config file to use keystone, local block-devices on the swift storage units (ie. no need to mount storage), and using openstack havana:

cat >swift.cfg <<END
swift-proxy:
    zone-assignment: auto
    replicas: 3
    auth-type: keystone
    openstack-origin: cloud:precise-havana/updates
swift-storage:
    zone: 1
    block-device: /etc/swift/storagedev1.img|2G
    openstack-origin: cloud:precise-havana/updates
keystone:
    admin-token: somebigtoken
    openstack-origin: cloud:precise-havana/updates
END

Deploy it (this could probably be replaced with a charm bundle?):

juju deploy --config=swift.cfg swift-proxy
juju deploy --config=swift.cfg --num-units 3 swift-storage
juju add-relation swift-proxy swift-storage
juju deploy --config=swift.cfg keystone
juju add-relation swift-proxy keystone

Once everything is up and running, create a tenant and user with the user having admin rights for the tenant (using your keystone unit’s IP address for keystone-ip). Note, below I’m using the names of tenant, user and role – which works with keystone 0.3.2, but apparently earlier versions require you to use the uuids instead. Check with `keystone help user-role-add`).

$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken tenant-create --name mytenant
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-create --name myuser --tenant mytenant --pass userpassword
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-role-add --tenant mytenant --user myuser --role Admin

And finally, use our new admin user to create a container for use in our dev environment (specify auth version 2):

$ export OS_REGION_NAME=RegionOne
$ export OS_TENANT_NAME=mytenant
$ export OS_USERNAME=myuser
$ export OS_PASSWORD=userpassword
$ export OS_AUTH_URL=http://keystone-ip:5000/v2.0/
$ swift -V 2 post mycontainer

If you want the container to be readable without auth:

$ swift -V 2 post mycontainer -r '.r:*'

If you want another keystone user to have write access:

$ swift -V 2 post mycontainer -w mytenant:otheruser

Verify that the container is ready for use:
$ swift -V 2 stat mycontainer

Please let me know if you spot any issues (these notes are from a month or two ago, so I haven’t just tried this).


Filed under: Uncategorized

Read more
Michael

Just documenting for later (and for a friend and colleague who needs it now) – my notes for setting up openstack swift using juju. I need to go back and check whether keystone is required – I initially had issue with the test auth so switched to keystone.

First, create the config file to use keystone, local block-devices on the swift storage units (ie. no need to mount storage), and using openstack havana:

cat >swift.cfg <<END
swift-proxy:
    zone-assignment: auto
    replicas: 3
    auth-type: keystone
    openstack-origin: cloud:precise-havana/updates
swift-storage:
    zone: 1
    block-device: /etc/swift/storagedev1.img|2G
    openstack-origin: cloud:precise-havana/updates
keystone:
    admin-token: somebigtoken
    openstack-origin: cloud:precise-havana/updates
END

Deploy it (this could probably be replaced with a charm bundle?):

juju deploy --config=swift.cfg swift-proxy
juju deploy --config=swift.cfg --num-units 3 swift-storage
juju add-relation swift-proxy swift-storage
juju deploy --config=swift.cfg keystone
juju add-relation swift-proxy keystone

Once everything is up and running, create a tenant and user with the user having admin rights for the tenant (using your keystone unit’s IP address for keystone-ip). Note, below I’m using the names of tenant, user and role – which works with keystone 0.3.2, but apparently earlier versions require you to use the uuids instead. Check with `keystone help user-role-add`).

$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken tenant-create --name mytenant
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-create --name myuser --tenant mytenant --pass userpassword
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-role-add --tenant mytenant --user myuser --role Admin

And finally, use our new admin user to create a container for use in our dev environment (specify auth version 2):

$ export OS_REGION_NAME=RegionOne
$ export OS_TENANT_NAME=mytenant
$ export OS_USERNAME=myuser
$ export OS_PASSWORD=userpassword
$ export OS_AUTH_URL=http://keystone-ip:5000/v2.0/
$ swift -V 2 post mycontainer

If you want the container to be readable without auth:

$ swift -V 2 post mycontainer -r '.r:*'

If you want another keystone user to have write access:

$ swift -V 2 post mycontainer -w mytenant:otheruser

Verify that the container is ready for use:
$ swift -V 2 stat mycontainer

Please let me know if you spot any issues (these notes are from a month or two ago, so I haven’t just tried this).


Filed under: Uncategorized

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140107 Meeting Agenda


ARM Status

Nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   cking    core-1311-kernel    1 work item   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   sforshee    servercloud-1311-cloud-images    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    6 work items   
   rtg    core-1311-kernel    1 work item   


Status: Trusty Development Kernel

We’ve finished cleaning up some DKMS packages for Trusty and are
preparing for our first v3.13 based kernel upload to the archive.
This is specifically based on the latest v3.13-rc7 upstream kernel.
I would also like to remind everyone that the 12.04.4 point release is
now taking place on Thurs Feb 6. The kernel is currently frozen for
12.04.4 and we do not anticipate any respins at this time.
—–
Important upcoming dates:
Thurs Jan 23 – Alpha 2 (~2 weeks away)
Thurs Feb 6 – 12.04.4 Final Release (~4 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Nothing new to report this week.


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131217 Meeting Agenda


ARM Status

nothing new to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   sforshee    servercloud-1311-cloud-images    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    5 work items   
   rtg    core-1311-kernel    1 work item   


Status: Trusty Development Kernel

The master branch for Trusty remains rebased on the v3.12.4 upstream
stable kernel. Our unstable branch has most recently rebased to
v3.13-rc4. Again, we don’t anticipate a v3.13 based upload for Trusty
until after the new year.
I would also like to point out that the 12.04.4 point release was pushed
out by 2 weeks from Jan 23 to Feb 6. This will not have any impact on
the kernel, we will still plan on shipping with the kernel we currently
have going through -proposed.
—–
Important upcoming dates:
Thurs Dec 19 – Alpha 1 (~2 days away)
Thurs Jan 23 – Alpha 2 (~5 weeks away)
Thurs Feb 6 – 12.04.4 Final Release (~7 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

No new update this week.


Open Discussion or Questions? Raise your hand to be recognized

The next meeting will happen after the New Year. The next meeting will be January 7th, 2014.

Read more
Robie Basak

 Meeting information

 

Meeting summary

This meeting was particularly quiet, presumably due to the upcoming holidays.

Actions still outstanding:

  • gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html

Scott linked to http://kernel.ubuntu.com/benchmarking/, which he said is really nice benchmark data that the kernel team are working on.

Robie reported on the status of upstreaming mongodb armhf and arm64 portability patches.

Due to the holidays, the next meeting will be at Tue, 7 Jan 2014 16:00:00 +0000.

 

Action items

  • (carried over) gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html

 

People present (lines said)

  • rbasak (26)
  • smoser (5)
  • meetingology (3)
  • caribou_ (2)
  • jamespage (2)
  • psivaa (1)
  • hallyn_ (1)
  • smb (1)

 

Full Log

  • 16:09 <rbasak> #startmeeting ubuntu-server-team

    16:09 <meetingology> Meeting started Tue Dec 17 16:09:17 2013 UTC. The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

    16:09 <meetingology>

    16:09 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired

    16:09 <rbasak> #topic Review ACTION points from previous meeting 16:09 * rbasak gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html (smoser, 16:04)

    16:10 <jamespage> still outstanding

    16:10 <rbasak> OK, thanks.

    16:10 <rbasak> #topic T Development Opening

    16:11 <rbasak> I’ve changed the agenda item to “T Development” for next time.

    16:11 <rbasak> Anything to note?

    16:11 <jamespage> alpha-1 this week

    16:11 <rbasak> #topic Server & Cloud Bugs (caribou)

    16:12 <rbasak> caribou_: hi!

    16:12 <caribou_> nothing here

    16:14 <rbasak> #topic Weekly Updates & Questions for the QA Team (psivaa)

    16:14 <psivaa> no updates from us as well

    16:14 <rbasak> Any questions for psivaa?

    16:14 <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb)

    16:14 <smb> nothing to report. Are there questions?

    16:15 <rbasak> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

    16:15 <smoser> hm..

    16:15 <smoser> go back one.

    16:15 <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb)

    16:15 <smoser> kernel team has *really* nice benchmark data that they’re working on

    16:15 <smoser> http://kernel.ubuntu.com/benchmarking/

    16:16 <smoser> the data there may change formats or content, but its good too look at.

    16:16 <rbasak> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

    16:17 <rbasak> I’ve been working on upstreaming portability patches for mongodb for armhf and arm64. This is reviewed upstream now and should land soon. Then I’ll see if I can get Debian updated to a cherry-pick of the upstream patches.

    16:17 <rbasak> No other updates. Any questions for me?

    16:17 <rbasak> #topic Ubuntu Server Team Events

    16:17 <rbasak> Christmas, I guess, is the reason why it’s quiet.

    16:18 <rbasak> Any other new upcoming events?

    16:18 <rbasak> #topic Open Discussion

    16:18 <rbasak> #topic Announce next meeting date, time and chair

    16:18 <caribou_> Ho Ho Ho

    16:19 <rbasak> Due to the holidays, I propose that our next meeting should be in January when we’re all back. Any objections?

    16:19 <hallyn_> nope

    16:20 <rbasak> So the next meeting will be at: Tue, 7 Jan 2014 16:00:00 +0000.

    16:20 <rbasak> Looks like next on the chair rota is roaksoax, so he’ll be chairing. I know roaksoax is on holiday now, so I’ll let him know by email.

    16:20 <rbasak> #endmeeting

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

MeetingLogs/Server/20131217 (last edited 2013-12-17 16:47:06 by racb)

Read more
Victor Palau

Hi,

I found myself trying to build a QML Ubuntu Touch app project that includes a qml c++ extension and I found that I some how stumble a bit along the way. So, here are some of my notes on how I got it done. Hope that helps.

Creating the project.

Using QtCreator, create a new project and select – QML Extension Library + Tabbed Touch.  I found that it was easier to change the QML side of things than start with an extension and then add the whole project structure.

Build and Run your project locally

In QtCreator click on projects.  In Build, I set up the build path as my project root path. In run,  the executable is “/usr/bin/qmlscene” (make sure there is no spaces trailing) and then Arguments is set to “-I  ../backend/modules $@ yourapp.qml”, with a working directory of “projectroot/app”

Now if you try to run your project it should build it locally and run your app. After that you are on a roll.

Build on target device

Click Ctrl+f11 should install the platform developer tools in your device. However, I how found that this lately does not work.

Instead from the terminal:

first we will need to make the image in your device writeable:
adb shell touch /userdata/.writable_image  --> and reboot the phone.
then:
cd /usr/share/qtcreator/ubuntu/scripts
adb devices
./device_developertools_install <device_id>

Now you are ready to build, so back to QtCreator:

Build>Ubuntu>Build Application on Device

This should build the application with only some test problems, but the main binaries would be created. To package your app you will need to get

/home/phablet/dev_tmp/<yourapp>/backend/modules/lib<yourlib>.so

Creating a click package

create a manifest standard manifest file. Manifest.json

{
"description": "your text",
"framework": "ubuntu-sdk-13.10",
"hooks": {
"yourappname": {
"apparmor": "yourappname.json",
"desktop": "yourappname.desktop"
}
},
"maintainer": "your name<yourname@yourmail.com>",
"name": "com.ubuntu.developer.yourname.yourappname",
"title": "yourappname",
"version": "0.1",
"architecture": "armhf"
}

You will also need a yourapp.desktop file:

[Desktop Entry]
Name=yourappname
Comment=description
Exec=qmlscene -I plugin $@ yourapp.qml
Icon=icon.png
Terminal=false
Type=Application
X-Ubuntu-Touch=true

Note that Exec= has a -I plugin part to it. This is very important, will see later.

Now yourapp.json file that contains your confinement profile:

{
"policy_groups": [
"networking"
],
"policy_version": 1
}

Now time to setup a folder with all this stuff, not that the plugin folder is going to contain your lib which your are importing with -I option on the desktop file:
myproject>
-./click/
--icon.png
--manifest.json
--yourapp.json
--yourapp.desktop
--./plugin/
---./yourlib/
----lib(yourlibname).so
----qmldir

Now you are ready to build from your project root folder:
click build ./click

This should create a .click file in your project folder.

Installing in your device

adb pull your.click /home/phablet/
adb shell
su phablet
cd ~
pkcon -p install-local your.click

This should be enough, but sometimes I find that you need to restart unity:
pkill unity8 (you might need sudo)


Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131210 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   sforshee    servercloud-1311-cloud-images    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    5 work items   
   rtg    core-1311-hwe-plans    1 work item   
      core-1311-kernel    1 work item   


Status: Trusty Development Kernel

The master branch for trusty has been rebased to the latest v3.12.4
upstream stable kernel. We also continue to track the latest v3.13
kernel on our unstable branch and most recently rebased to v3.13-rc3.
We anticipate uploading a v3.13 based Trusty kernel to the archive after
the new year.
—–
Important upcoming dates:
Thurs Dec 19 – Alpha 1 (~1 week away)
Thurs Jan 23 – Alpha 2 (~6 weeks away)
Thurs Dec 12 – 12.04.4 Kernel Freeze (this week!)
Thurs Jan 23 – 12.04.4 Final Release (~6 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Verification & Regression Testing
  • Precise – Verification & Regression Testing
  • Quantal – Verification & Regression Testing
  • Raring – Verification & Regression Testing
  • Saucy – Verification & Regression Testing
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131203 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

First, a big thank you to apw for wrestling our kernel related
blueprints and work items into place to make the above links useful
again. Our work items and owners are as follows:

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    3 work items   
      core-1311-hwe-plans    1 work item   
      core-1311-secure-boot    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   cking    core-1311-kernel    2 work items   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    5 work items   
   rtg    core-1311-hwe-plans    1 work item   
      core-1311-kernel    1 work item   


Status: Trusty Development Kernel

The master branch for trusty has been rebased to the latest v3.12.2
upstream stable kernel. We also continue to track the latest v3.13
kernel on our unstable branch and most recently rebased to v3.13-rc2.
Again, we shall switch our master branch from tracking v3.12 to v3.13
once we cycle through the initial -rc’s and feel it is stable enough for
wider consumtion, ie uploaded to the archive.
—–
Important upcoming dates:
Thurs Dec 19 – Alpha 1 (~2 weeks away)
Thurs Jan 23 – Alpha 2 (~7 weeks away)
Thurs Dec 12 – 12.04.4 Kernel Freeze (~1 week away)
Thurs Jan 23 – 12.04.4 Final Release (~7 weeks away)

  • NOTE: Even though the kernel freeze date for 12.04.4 is Dec 12,
    patches needed to have landed in the SRU cadence starting
    this week to make the 12.04.4 point release. Contact us
    *immediately* if there are patches which need to land.

    https://lists.ubuntu.com/archives/kernel-team/2013-November/034753.html


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Prep’ing
  • Precise – Prep’ing
  • Quantal – Prep’ing
  • Raring – Prep’ing
  • Saucy – Prep’ing
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131126 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

While marginally useful for tracking work items in the past, the above
links are completely useless at the moment. I have manually reviewed
work items from the core-1311-kernel and core-1311-hwe-plans blueprints.
However, beyond those two, I’m oblivious to what other work our team or
individuals were signed up for.

   apw    core-1311-kernel    1 work ite   
   cking    core-1311-kernel    2 work item   
   rtg    core-1311-hwe-plans    1 work item   


Status: Trusty Development Kernel

For those unaware, the ubuntu-trusty git repo is open and available at:
git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git . The master branch is
currently tracking the latest 3.12.1 upstream stable kernel while the
unstable branch has most recently been rebased to v3.13-rc1. We shall
move our master branch to track v3.13 after some baking. We will also
upload to the archive when it’s ready.
—–
Important upcoming dates:
Thurs Dec 12 – 12.04.4 Kernel Freeze (~2 weeks away)
Thurs Dec 23 – 12.04.4 Final Release (~8 weeks away)
Thurs Dec 19 – Alpha 1 (~3 weeks away)
Thurs Jan 23 – Alpha 2 (~ 8 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Regression Testing
  • Precise – Regression Testing
  • Quantal – Regression Testing
  • Raring – Regression Testing
  • Saucy – Regression Testing
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Steve George

Recently some concerns were expressed by fixubuntu.com, a website focusing on Ubuntu privacy, about a routine trademark enforcement email that Canonical sent. We want to provide some context around this issue.

In Ubuntu we cherish an open and diverse discourse, and we welcome differing and challenging views and perspectives; it is the cornerstone of our community, as exemplified by our open Ubuntu Developer Summit, mailing lists, IRC channels and more. Our Code of Conduct and Trademark policy simply provide guardrails for those conversations to flourish.

Canonical owns the family of Ubuntu trademarks and we have a responsibility to protect those trademarks. In trademark law a mark owner is expected to protect the authenticity of a trademark otherwise they risk losing the mark.

Our trademark policy is unusually permissive. We have a global community of Ubuntu contributors, LoCo teams, translators, developers, advocates, and others who want to use these marks to within the spirit and governance of the project. Therefore, our policy has been crafted in such a way that we can protect the marks and what they stand for, but also ensure our community has the freedom to use them.

In the case of fixubuntu.com, we were concerned that the use of the trademark implied a connection with and endorsement from the Ubuntu project which didn’t exist. The site owner has already agreed to remove the Ubuntu logo and clarified that there is no connection; from our perspective the situation has been resolved, and we have no issue with the site or the criticism it includes.  In fact, far from an trying to silence critics, our trademark policy actually calls out parody and criticism and other uses as being allowed when the marks are used appropriately.  (Please make the parodies funny – we need a good laugh as much as anyone!)

We aim to communicate our policies and actions clearly and openly, and I welcome feedback on how to do that better.

UPDATE:  I should have mentioned that we do listen closely to constructive criticism and user’s requests about the Online Search function. And in response we already added a simple way for you to limit your search to local results only if you wish.  If you’re running the latest version of Ubuntu, check Settings -> Security & Privacy -> Search.

Read more
Michael

I’ve been working on some more support for ansible in the juju charm-helpers package recently [1], which has effectively transformed my juju charm’s hooks.py to something like:

# Create the hooks helper, passing a list of hooks which will be
# handled by default by running all sections of the playbook
# tagged with the hook name.
hooks = charmhelpers.contrib.ansible.AnsibleHooks(
    playbook_path='playbooks/site.yaml',
    default_hooks=['start', 'stop', 'config-changed',
                   'solr-relation-changed'])

@hooks.hook()
def install():
    charmhelpers.contrib.ansible.install_ansible_support(from_ppa=True)

And that’s it.

If I need something done outside of ansible, like in the install hook above, I can write a simple hook with the non-ansible setup (in this case, installing ansible), but the decorator will still ensure all the sections of the playbook tagged by the hook-name (in this case, ‘install’) are applied once the custom hook function finishes. All the other hooks (start, stop, config-changed and solr-relation-changed) are registered so that ansible will run the tagged sections automatically on those hooks.

Why am I excited about this? Because it means that practically everything related to ensuring the state of the machine is now handled by ansibles yaml declarations (and I trust those to do what I declare). Of coures those playbooks could themselves get quite large and hard to maintain, but ansible has plenty of ways to break up declarations into includes and roles.

It also means that I need to write and maintain fewer unit-tests – in the above example I need to ensure that when the install() hook is called that ansible is installed, but that’s about it. I no longer need to unit-test the code which creates directories and users, ensures permissions etc., or even calls out to relevant charm-helper functions, as it’s all instead declared as part of the machine state. That said, I’m still just as dependent on integration testing to ensure the started state of the machine is what I need.

I’m pretty sure that ansible + juju has even more possibilities for being able to create extensible charms with plugins (using roles), rather than forcing too much into the charms config.yaml, and other benefits… looking forward to trying it out!

[1] The merge proposal still needs to be reviewed, possibly updated and landed :)


Filed under: Uncategorized

Read more
Michael

I’ve been working on some more support for ansible in the juju charm-helpers package recently [1], which has effectively transformed my juju charm’s hooks.py to something like:

# Create the hooks helper, passing a list of hooks which will be
# handled by default by running all sections of the playbook
# tagged with the hook name.
hooks = charmhelpers.contrib.ansible.AnsibleHooks(
    playbook_path='playbooks/site.yaml',
    default_hooks=['start', 'stop', 'config-changed',
                   'solr-relation-changed'])

@hooks.hook()
def install():
    charmhelpers.contrib.ansible.install_ansible_support(from_ppa=True)

And that’s it.

If I need something done outside of ansible, like in the install hook above, I can write a simple hook with the non-ansible setup (in this case, installing ansible), but the decorator will still ensure all the sections of the playbook tagged by the hook-name (in this case, ‘install’) are applied once the custom hook function finishes. All the other hooks (start, stop, config-changed and solr-relation-changed) are registered so that ansible will run the tagged sections automatically on those hooks.

Why am I excited about this? Because it means that practically everything related to ensuring the state of the machine is now handled by ansibles yaml declarations (and I trust those to do what I declare). Of coures those playbooks could themselves get quite large and hard to maintain, but ansible has plenty of ways to break up declarations into includes and roles.

It also means that I need to write and maintain fewer unit-tests – in the above example I need to ensure that when the install() hook is called that ansible is installed, but that’s about it. I no longer need to unit-test the code which creates directories and users, ensures permissions etc., or even calls out to relevant charm-helper functions, as it’s all instead declared as part of the machine state. That said, I’m still just as dependent on integration testing to ensure the started state of the machine is what I need.

I’m pretty sure that ansible + juju has even more possibilities for being able to create extensible charms with plugins (using roles), rather than forcing too much into the charms config.yaml, and other benefits… looking forward to trying it out!

[1] The merge proposal still needs to be reviewed, possibly updated and landed :)


Filed under: Uncategorized

Read more
Ameet Paranjape

The bread and butter of Landscape is security compliance – keeping your systems securely up to date with minimum effort, and remedy any unintended side-effects an update may have.  Helping your CIO prove this was done timely is a neat additional capability that can save the IT team the need to scrub logs to create reports.

“Help me keep my Ubuntu systems compliant with the latest security updates” is a common request I hear from frustrated System Administrators.  Landscape was designed with compliance in mind from the start, but since I have explained and demonstrated this countless times to many customers in person, I thought I’d share the benefits of managing updates through Landscape with a larger audience.

The “freshness” of Ubuntu, this wonderful ability to find any and all software, in the latest version, always readily packaged for your favorite distribution, comes with a constant stream of updates that need to be managed.

To start, let’s first approach this using a reactive method and finish with a proactive approach that will keep our systems compliant going forward.

In Landscape, select the “COMPUTERS” tab.

 Under Select Computers choose “All” as shown below.  In my case, I have 5 servers but you could have any number of physical servers, desktops,  virtual machines or cloud  guests under management in your account.

Select the “Packages” tab on the right:

In the Summary section of my example, I have “3 computers with security updates to install” link.  You could have hundreds, thousands or even tens of thousands of managed systems – the strength of Landscape’s interface is how it makes it as simple to manage a thousand systems as it is to manage one.

Landscape lets you easily distinguish between security updates, and feature updates and bug fixes – so if you desire to reduce the amount of changes you push to your systems, or to schedule a different maintenance event for less urgent updates, this is easily done.

Select the link to get a complete list of security fixes and select “All upgrades.” This will toggle the install selection of all the security updates listed – Landscape lets you select a different behavior for each of the security updates listed, from the same overview screen. One could, for example, select to uninstall cups altogether if the vulnerable systems do not support any actual printing.  This is done through the three buttons on the left.

The selected action is reflected in the color change:

Scroll to the bottom of the screen and select Apply Changes.  You can apply the updates right away or select a future date and time. As an aside, I strongly recommend using Landscape’s system tagging feature for rolling updates and avoiding regressions, by grouping similar systems together based on their workloads

.

At this point all our systems will have the latest Ubuntu security updates installed shortly.

Now let’s examine how to keep systems current proactively by using Landscape’s package profiles feature. From the Landscape tab,  select Profiles.

In the next window, select Upgrade Profiles.

Click on “Add update profile” and enter in the required fields.  The title of this profile is “Ubuntu Security Updates” but you could name your profile whatever you want.  We have checked the “only security updates” box so this profile won’t apply feature updates or bugfixes, and requested the packages be applied on all systems at 2am every Sunday.  Click the Save button and it will take effect.

Profiles are editable, and you can combine profiles with Landscape’s system tags for granular control of the update process.  A common example is using different scheduled update profiles for roaming devices: you could mandate after-hours updates for the laptops of your sales team to enforce your security policy, yet make sure that no lingering Landscape tasks interfere with their work hours if the systems were offline or powered off overnight.

Sometimes, an update does not go exactly as planned.  Packages are hardly ever defective on their own, but sometimes an update may be having an unintended side effect on your workload, and you need to roll back the patch you just installed to continue operating until a more complete or fully functional solution can be devised.

Landscape makes this remarkably easy. Searching for and selecting the offending package is done in the packages tab, and expanding the details section will show what managed devices have the package installed, and what versions it can be reverted to.  Once you are ready to commit, the downgrade process is just as streamlined as the upgrade.

Many of our customers have Compliance or Governance requirements: they need to prove to an oversight body, either internally to their company or externally to a certification authority, that systems were kept secure.  The most common example of this is the PCI DSS rule requiring security updates be rolled out within 30 days of release.

You can help your CIO fulfill these requirements effortlessly, by providing her with a CSV or a chart showing the current state of update of your infrastructure, generated using Landscape’s reporting functionality:

Even when no security audits have to be met, folks are pretty happy when you show a high percentage of systems are securely patched  and you can justify the groups of systems that have yet to be covered.  Auditing is awesome, as it generates CSV data and charts without requiring you to spend any cycles sifting through logs gathering details.

This is just one of the many compliance options available in Landscape.  You can watch a four-minute video overview on YouTube,  or Check out Landscape yourself.

Read more
Victor Palau

It has been over 2 months since the Ubuntu Edge campaign concluded, and I haven’t really blogged about it.  I must say, driving something like this was great fun but also a fully immersive 24-7 experience. For that reason, I wanted some time to pass before write some conclusions about it.

One of the things that made the Ubuntu Edge campaign to stand out from previous crowd funding projects was the target: $32 Million. Other successful projects (I will focus only on products) had much lower targets (~$100K). So, why was this the case?

If your company has already raised capital via “standard” funding routes or you are actively pursuing it, a successful crowd funding campaign will reduce the overall amount of equity you have to give away. It can also attract that elusive VC investment.  In this situation, your objectives are:

  • Proof the product viability 
  • Remove doubts from future investors minds
  • ensure your campaign and your product are perceived as a successes

An early achievement of your campaign target will tick all these boxes. A “sold out” effect in the first week will increase the confidence of future pledgers and investors. In that case, a campaign target of $100K can be the magic number for you. 

In the other hand, if crowd funding is your only or main avenue to finance your product, your objectives will be slightly different. These were ours:

  • Proof the product viability
  • Finance product design and factory tooling
  • Finance a fix/minimum production run
  • Market validation

An early achievement of your target is still desirable, but your main worry will be to raise enough money via the campaign to deliver on your promises to the pledgers.

Although we raised over $12 Million, we did not reach our intended target. The Ubuntu Edge was a unique proposition that was build on the premise of delivering the latest cutting edge technology.  Unfortunately, this meant that we could not pursue what I think is a better approach for 100% crowd funded products: a multi-campaign project.

In a crowd funding campaign, people contribute for different reasons:

  • The Angels: Angels are interested in supporting new innovation. They might not even necessarily want to own your product, but they appreciate the disruption you are trying to bring to the market.  For these reason, they are willing to contributed from a little as $1 to thousands of dollars to see your project succeed.
  • The Extended Team: These are passionate individuals that understand your product concept and they want one! Not only they are willing to part with some money to get one, but they are also willing to contribute their own time and energy to make your product successful. They are a great source of professional and amateur resources. The contributions we got for Ubuntu Edge ranged from advise on how to run the campaign by serious knowledge people, to PR (T-shirt designs, websites, ads) to product design.
  • The Pragmatists:  Your product might look good, but your project might just be too risky. Crowd funding projects are developing a bit of a reputation for shipping late or even worst, never happening.  Pragmatist might be put off from contributing to your project is the perceived risk is too high.  Some key questions they would like answer to are: Who are you? What is your proven record? Do you have a proto-type working?  Do you have suppliers ready to go? but they all ultimately boil down to one: Can I trust you?
  • The Shoppers: Although, it should be clear to everyone that crowd funding is not the same that shopping in Amazon, similar motivations may apply.  Shoppers will compare backing your project with buying a similar product online. Things they will care about: Are you offering a good deal? How long will it take for me get the product? What warranties do you offer?.

Pragmatists and shoppers form the bulk of the backer community out in the wild. If you are just getting started with your product development, you might find that addressing the concerns of pragmatists and shoppers is just not possible. In that case, financing your product development via multiple crowd funding projects might be a better option.

Target your first project to attract angels and extended-team. Set a campaign target that will allow you to build a prototype and start seriously talking to suppliers. Build up your credibility by delivering the first project on time.

For your second project, you will have had reduced the risk and the time to product delivery substantially. You might now be able to raise the rest of the funding or your might need a couple more iterations. Here is how the people at +Pool are doing it:

  1. First project
  2. second project

 

+POOL

 


Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131022 Meeting Agenda


ARM Status

Nothing to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

Nothing to report here until after vUDS Nov 19-21.


Status: Trusty Development Kernel

The ubuntu-trusty git repo is officially open,
git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git . It’s been rebased to
the latest v3.12-rc6 upstream kernel. We have not yet uploaded to the
archive but will likely do so soon.
—–
Important upcoming dates:
Thurs Dec 19 – Alpha 1 for opt-in flavors (~8 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Oct. 15):

  • Lucid – Building Kernels
  • Precise – Building Kernels
  • Quantal – Building Kernels
  • Raring – Building Kernels
  • Saucy – Building Kernels
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

The next kernel team meeting will be after vUDS on November 26th, 2013.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131015 Meeting Agenda


ARM Status

S/master-next: fixes for the SATA bus present on the imx6 board were
committed, while support for a new imx6-variant (wandboard) is under
investigation.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    foundations-1305-arm64-bringup    2 work items   


Status: Saucy Development Kernel

We are ~2 days away from 13.10′s Final Release. The kernel remains
frozen and we do not anticipate any further uploads before release. All
patches coming in at this time are being queued for SRU.
—–
Important upcoming dates:
Thurs Oct 17 – 13.10 Release (~2 days away)


Status: CVE’s

== 2013-10-15 ==
The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Oct. 15):

  • Lucid – Verification and Regression Testing
  • Precise – Verification and Regression Testing
  • Quantal – Verification and Regression Testing
  • Raring – Verification and Regression Testing
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No Open Discussion.

Read more
bigjools

I have had a reasonable amount of success with the Rifampicin.  My heart palpitations pretty much stopped over the course of a couple of weeks and stayed away until the end of that prescription.  My doctor put me on a doubled dose for another 6 weeks so let’s see how that goes…

In the meantime, the palpitations came back a little.  I’m not sure whether this is because I had a 4 day gap between courses or whether it’s part of a herx or otherwise caused by the increased dose.

I’m committed to flying across the Pacific at the weekend (I’m going to San Francisco for a week) — I hope I don’t get an attack on the plane :(


Read more
ZhengPeng Hou

lxc and openvswtich

Intended to use ovs with lxc before, but lxc only support linux bridge:

int lxc_bridge_attach(const char *bridge, const char *ifname)
{
int fd, index, err;
struct ifreq ifr;

if (strlen(ifname) >= IFNAMSIZ)
return -EINVAL;

index = if_nametoindex(ifname);
if (!index)
return -EINVAL;

process_lock();
fd = socket(AF_INET, SOCK_STREAM, 0);
process_unlock();
if (fd < 0)
return -errno;

strncpy(ifr.ifr_name, bridge, IFNAMSIZ);
ifr.ifr_ifindex = index;
err = ioctl(fd, SIOCBRADDIF, &ifr);
process_lock();
close(fd);
process_unlock();
if (err)
err = -errno;

return err;
}

here we can see only linux bridg supported, if you try to attach to ovs, it fails.
with help from a friend, had some changes here:


--- lxc-1.0.0~alpha1.orig/src/lxc/network.c 2013-09-11 06:22:00.000000000 +0800
+++ lxc-1.0.0~alpha1/src/lxc/network.c 2013-10-12 22:01:28.926679880 +0800
@@ -986,6 +986,9 @@
{
int fd, index, err;
struct ifreq ifr;
+ struct stat sb;
+ char brdirname[22 + IFNAMSIZ + 1] = {0};
+ char ovscmd[20 + IFNAMSIZ * 2 + 1] = {0};

if (strlen(ifname) >= IFNAMSIZ)
return -EINVAL;
@@ -993,6 +996,15 @@
index = if_nametoindex(ifname);
if (!index)
return -EINVAL;
+ snprintf(brdirname, 22 +IFNAMSIZ + 1, "/sys/class/net/%s/bridge", bridge);
+ if (stat(brdirname, &sb) == -1) {
+ if (errno == ENOENT) {
+ snprintf(ovscmd, 20 + IFNAMSIZ * 2 + 1, "ovs-vsctl add-port %s %s", bridge, ifname);
+ err = system(ovscmd);
+ } else {
+ err = -EINVAL;
+ }
+ } else if (S_ISDIR(sb.st_mode)) {

fd = socket(AF_INET, SOCK_STREAM, 0);
if (fd < 0)
@@ -1004,7 +1016,9 @@
close(fd);
if (err)
err = -errno;
-
+ } else {
+ err = -EINVAL;
+ }
return err;
}

This patch was made for lxc in ubuntu 13.10, I have it build in my ppa. binary package can be found from my ppa
ppa:zhengpeng-hou/dev.
So now, I have all my containers bridged to my home network directly.
https://docs.google.com/file/d/0BwNEP6aM800AMUhHcDdQb3B1NEU/edit?usp=sharing

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131008 Meeting Agenda


ARM Status

VIRTIO_[BLK|MMIO|NET] support (to be used with qemu 1.6) was turned on, and some
fixes for highbank/s nic landed in S/generic.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    foundations-1305-arm64-bringup    2 work items   
   cking    foundations-1308-power-measurement    1 work item   


Status: Saucy Development Kernel

We are ~2 days away from Final Freeze. We do however expect additional
kernel uploads hopefully by EOD today for both phablet and distro
kernels. These uploads will primarily provide some critical bug fixes
for AppArmor. Additionally, for the distro kernel we may take advantage
of this upload opportunity to land some patches we were queuing for SRU.
All the patches in question are documented at each of the following bug
reports: LP:1208988, LP:1218004, LP:1235523, LP:1235973, LP:1235977,
LP:1235161, LP:1235914. Beyond this, we do not anticipate any further
uploads until the first round of kernel SRU’s following 13.10′s release.
Also having passed Kernel Freeze last week, I’ll plan on sending out the
obligatory emails regarding Saucy’s final kernel version and configuration.
—–
Important upcoming dates:
Thurs Oct 10 – Final Freeze (~2 days away)
Thurs Oct 17 – 13.10 Release (~1 week away)


Status: CVE’s

== 2013-10-08 ==
The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Oct. 8):

  • Lucid – Verification and Regression Testing
  • Precise – Verification and Regression Testing
  • Quantal – Verification and Regression Testing
  • Raring – Verification and Regression Testing
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Yolanda Robla

Agenda

 

Minutes

 

Meeting information

 

Meeting summary

 

Review ACTION points from previous meeting

The discussion about “Review ACTION points from previous meeting” started at 16:02.

 

Saucy Development

The discussion about “Saucy Development” started at 16:07.

 

Server & Cloud Bugs (caribou)

The discussion about “Server & Cloud Bugs (caribou)” started at 16:45.

 

Weekly Updates & Questions for the QA Team (psivaa)

The discussion about “Weekly Updates & Questions for the QA Team (psivaa)” started at 16:46.

 

Weekly Updates & Questions for the Kernel Team (smb)

The discussion about “Weekly Updates & Questions for the Kernel Team (smb)” started at 16:46.

 

Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

The discussion about “Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)” started at 16:47.

 

Ubuntu Server Team Events

The discussion about “Ubuntu Server Team Events” started at 16:48.

 

Open Discussion

The discussion about “Open Discussion” started at 16:49.

 

Announce next meeting date and time

The discussion about “Announce next meeting date and time” started at 16:52.

 

Vote results

 

Action items

  • (none)

 

People present (lines said)

  • yolanda (65)
  • jamespage (33)
  • ubottu (13)
  • rbasak (12)
  • zul (7)
  • roaksoax (3)
  • meetingology (3)
  • adam_g (2)
  • smb (1)
  • caribou (1)
  • psivaa (1)
  • hallyn (1)

 

Full Log

  • 16:02 <yolanda> #startmeeting ubuntu-server-team

    16:02 <meetingology> Meeting started Tue Oct 1 16:02:14 2013 UTC. The chair is yolanda. Information about MeetBot athttp://wiki.ubuntu.com/meetingology.

    16:02 <meetingology>

    16:02 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired

    16:02 <yolanda> #topic Review ACTION points from previous meeting

    16:02 <yolanda> smoser look at / assign bug 1206872 and bug 1156932

    16:02 <ubottu> bug 1206872 in samba (Ubuntu Saucy) “samba needs a config.sub update to support aarch64″ [Medium,Triaged]https://launchpad.net/bugs/1206872

    16:02 <ubottu> bug 1156932 in python-novaclient (Ubuntu Saucy) “User can’t modify security-group-rule via nova-api if there are duplicated security group name” [High,Confirmed] https://launchpad.net/bugs/1156932

    16:03 <yolanda> smoser *

    16:03 <yolanda> ^

    16:04 <yolanda> anyone has feedback about that?

    16:06 <jamespage> novaclient won’t fix that I suspect

    16:06 <jamespage> yolanda, bug 1206872 is not specifically important for server this cycle

    16:06 <ubottu> bug 1206872 in samba (Ubuntu Saucy) “samba needs a config.sub update to support aarch64″ [Medium,Triaged]https://launchpad.net/bugs/1206872

    16:06 <jamespage> so I’d skip that

    16:07 <yolanda> so we postpone that?

    16:07 <yolanda> ok , let’s continue

    16:07 <yolanda> #topic Saucy Development

    16:08 <yolanda> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule

    16:08 <yolanda> #subtopic Release Bugs

    16:08 <yolanda> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server

    16:09 <yolanda> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455

    16:09 <ubottu> Ubuntu bug 1208455 in linux (Ubuntu Saucy) “general protection fault running apt-get inside double nested kvm VM” [High,In progress]

    16:09 <hallyn> smb: ^

    16:10 <yolanda> smb not here, let’s continue…

    16:11 <yolanda> https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1213915

    16:11 <ubottu> Ubuntu bug 1213915 in ceph (Ubuntu Saucy) “Please demote ceph-mds and ceph-fs-common to universe” [High,New]

    16:12 <jamespage> still with archive-admins

    16:12 <yolanda> https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1199791

    16:12 <ubottu> Ubuntu bug 1199791 in nova (Ubuntu Saucy) “nova-compute-xcp misses nova-compute.conf” [High,Triaged]

    16:12 <jamespage> just pinged one

    16:12 <jamespage> zul,

    16:12 <zul> not done

    16:13 <yolanda> https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1223010

    16:13 <ubottu> Ubuntu bug 1223010 in keystone (Ubuntu Saucy) “Use oauthlib rather than oauth.” [High,Triaged]

    16:13 <yolanda> zul ^

    16:13 <zul> working on it now

    16:13 <yolanda> https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1231901

    16:14 <ubottu> Ubuntu bug 1231901 in nagios3 (Ubuntu Saucy) “Installing Nagios3 and Apache2 in Saucy does not enable the cgi mod, which is required” [High,Triaged]

    16:15 <yolanda> jamespage ?

    16:15 <jamespage> yolanda, yeah – that popped up last friday

    16:15 <jamespage> rbasak, fyi

    16:15 <jamespage> I’ll pick that up this week

    16:15 <rbasak> I hadn’t seen that – thanks.

    16:16 <yolanda> ok

    16:16 <jamespage> rbasak, oh – unless you would like to – feel free

    16:16 <jamespage> it needs a2enmod cgi (which used to happen auto with mpm-prefork)

    16:16 <rbasak> jamespage: I’ll put it on my todo and let you know if I get to it first.

    16:16 <yolanda> https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1231970

    16:16 <ubottu> Ubuntu bug 1231970 in websockify (Ubuntu Saucy) “[FFe] nova-novncproxy requires websockify > 0.5 – please sync from unstable” [High,Triaged]

    16:18 <yolanda> zul ^

    16:18 <zul> watiting for release team

    16:18 <yolanda> ok

    16:18 <yolanda> https://bugs.launchpad.net/ubuntu/+source/python-cliff/+bug/1227167

    16:18 <ubottu> Ubuntu bug 1227167 in python-cliff (Ubuntu Saucy) “python-cliff needs to raise Build-Depends on pyparsing to 2.0.0″ [Medium,Triaged]

    16:19 <yolanda> jamespage / smoser ?

    16:19 <zul> that should be fixed already

    16:20 <jamespage> zul, can you check and close the bug if so please

    16:20 <yolanda> zul, i found today that there can be a problem with launchpad branches in python-cliff ?

    16:20 <zul> yolanda: ?

    16:20 <yolanda> ubuntu version was newer than the one downloaded from launchpad

    16:22 <yolanda> zul, python-cliff branch still points to 1.4-1ubuntu1, that is wrong, right?

    16:22 <zul> right

    16:22 <zul> ill have a look

    16:22 <yolanda> cool

    16:23 <yolanda> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1227353

    16:23 <ubottu> Ubuntu bug 1227353 in maas (Ubuntu Saucy) “Please promote maas-dns, maas-dhcp to main” [Undecided,New]

    16:23 <jamespage> action for roaksoax on that one

    16:23 <jamespage> roaksoax, please add to a suitable seed

    16:23 <jamespage> (do they need to go on the iso per-chance?)

    16:24 <roaksoax> jamespage: im uploading a new maas package today

    16:24 <jamespage> roaksoax, sounds like you are already on top of it great!

    16:24 <roaksoax> yep!

    16:24 <roaksoax> next upload should contain a fix

    16:25 <yolanda> https://bugs.launchpad.net/uvtool/+bug/1228228

    16:25 <ubottu> Ubuntu bug 1228228 in cloud-init (Ubuntu Saucy) “ubuntu is not added to sudo group” [Undecided,Triaged]

    16:25 <rbasak> This is pending a cloud-init upload I think.

    16:25 <rbasak> smoser?

    16:27 <yolanda> ok, let’s continue

    16:27 <yolanda> #subtopic Blueprints

    16:28 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2

    16:29 <yolanda> any updates for it? 16:29 * jamespage looks

    16:33 <yolanda> shall i continue?

    16:34 <yolanda> jamespage ^

    16:35 <jamespage> its OK

    16:35 <jamespage> only one todo outstanding

    16:35 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init

    16:36 <yolanda> smoser ^?

    16:37 <jamespage> yolanda, smoser not around right now

    16:37 <yolanda> next one …

    16:37 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery

    16:37 <jamespage> thats OK

    16:38 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2

    16:38 <jamespage> just waiting on final release

    16:38 <jamespage> roaksoax,

    16:38 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph

    16:40 <yolanda> jamespage ^

    16:40 <jamespage> yolanda, aside from the radosgw geo-replication agents ceph is looking good

    16:40 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa

    16:41 <jamespage> that looks behind

    16:41 <jamespage> I suspect some items to slip to next release – adam_g?

    16:42 <adam_g> ya

    16:42 <adam_g> ill postpone accordingly now

    16:42 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana

    16:44 <jamespage> generally looking OK

    16:44 <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb

    16:44 <jamespage> we have one challenge in that OpenStack Havana and Saucy release on the same day

    16:44 <jamespage> so we will zero-day sru havana into saucy

    16:44 <jamespage> mongodb: not so great

    16:44 <jamespage> we won’t make the objective to make main this cycle

    16:44 <yolanda> so this will be postponed?

    16:45 <jamespage> yeah – just did

    16:45 <yolanda> ok

    16:45 <yolanda> let’s continue

    16:45 <yolanda> #topic Server & Cloud Bugs (caribou)

    16:45 <caribou> Nothing on my radar this week

    16:46 <yolanda> ok

    16:46 <yolanda> #topic Weekly Updates & Questions for the QA Team (psivaa)

    16:46 <psivaa> no updates from us Smile :)

    16:46 <yolanda> #topic Weekly Updates & Questions for the Kernel Team (smb)

    16:46 <smb> Hi, I have not really made much progress on the nested kvm issue. Did a bit of drbd8 investigation (bug 1185756) and looked into merging back xen-4.3 from Debian to reduce our delta. But I am a bit distracted at the moment by me moving next week. Which will also cause me not to be joining next weeks meeting.

    16:46 <ubottu> bug 1185756 in drbd8 (Ubuntu Precise) “drbd8-utils not compatible with linux-lts-raring kernel in 12.04″ [High,Confirmed]https://launchpad.net/bugs/1185756

    16:47 <yolanda> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

    16:47 <rbasak> No updates from me. Any questions?

    16:48 <yolanda> #topic Ubuntu Server Team Events

    16:48 <yolanda> anything apart from Cloud Summit and next ODS?

    16:49 <yolanda> #topic Open Discussion

    16:49 <rbasak> o/

    16:49 <rbasak> Need to nominate someone to drive ISO testing for 1) our final Saucy server images 2) subsequent releases. And do we need a process for this? See: http://irclogs.ubuntu.com/2013/09/30/%23ubuntu-release.html “does anyone have an insight on who is doing signoff for the server images?” –rbasak

    16:49 <rbasak> I’d put that in the agenda but I think you missed it.

    16:49 <rbasak> In the past, we end up with a last minute request from the release manager and scramble to find someone to do the ISO testing and put the results in the tracker.

    16:50 <rbasak> It’d be nice to have this planned in advance.

    16:51 <rbasak> jamespage or smoser: any comments?

    16:51 <jamespage> I’ll do it

    16:51 <rbasak> Thanks!

    16:52 <yolanda> ok, any more comments?

    16:52 <yolanda> let’s finish then…

    16:52 <yolanda> #topic Announce next meeting date and time

    16:52 <yolanda> Next meeting will be on Tue 8th of October

    16:52 <yolanda> chair will be adam_g

    16:53 <yolanda> #endmeeting

Read more