Canonical Voices

Posts tagged with 'uncategorized'

Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150728 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Kernel Prep
  • Trusty – Kernel Prep
  • lts-Utopic – Kernel Prep
  • Vivid – Kernel Prep
    Current opened tracking bugs details:
  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html
    Schedule:

    cycle: 26-Jul through 15-Aug
    ====================================================================
    24-Jul Last day for kernel commits for this cycle
    26-Jul – 01-Aug Kernel prep week.
    02-Aug – 08-Aug Bug verification & Regression testing.
    09-Aug – 15-Aug Regression testing & Release to -updates.


Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

Read more
Kick In

 

  • smoser to check with Odd_Bloke on status of high priority bug 1461242
  • Think about numad integration
  • Next meeting will be on Jul 29st 16:00:00 UTC in #ubuntu-meeting

Full agenda and log

 

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150721 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

We have rebased the master and master-next branch of our Wily repo to
4.1 and uploaded to the archive. We’ll move master-next to start
tracking 4.2.
—–
Important upcoming dates:

  • https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
    Thurs July 30 – Alpha 2 (~1 weeks away)
    Thurs Aug 6 – 14.04.3 (~2 weeks away)
    Thurs Aug 20 – Feature Freeze (~4 weeks away)
    Thurs Aug 27 – Beta 1 (~5 weeks away)


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 04-Jul through 25-Jul
    ====================================================================
    03-Jul Last day for kernel commits for this cycle
    05-Jul – 11-Jul Kernel prep week.
    12-Jun – 25-Jul Bug verification; Regression testing; Release
    ** NOTE: This cycle produces the kernel that will be in the 14.04.3
    point release.


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Michael

I was recently in the situation of wanting to transition traffic gradually from an old deployment to a new deployment. It’s a large production system, so rather than just switching the DNS entries to point at the new deployment, I wanted to be able to shift the traffic over in a couple of controlled steps.

It turns out, Apache’s mod_proxy makes this relatively straight forward. You can choose which resource for which you want to move traffic, and easily update the proportion of traffic for that resource which should go through to the new env. Might be old news to some, but not having needed this before, I was quite impressed by Apache2’s configurability:

# Pass any requests for specific-url through to the balancer (defined below)
# to transition traffic from the old to new system.
ProxyPass /myapp/specific-url/ balancer://transition-traffic/myapp/specific-url/
ProxyPassReverse /myapp/specific-url/ balancer://transition-traffic/myapp/specific-url/

# Send all other requests straight to the backend for the old system.
ProxyPass /myapp/ http://old.backend.ip:1234/myapp/
ProxyPassReverse /myapp/ http://backend.ip:1234/myapp/

# Send 50% of the traffic to the old backend, and divide the rest between the
# two new frontends.
<Proxy balancer://transition-traffic>
    BalancerMember http://old.backend.ip:1234 timeout=60 loadfactor=2
    BalancerMember http://new.frontend1.ip:80 timeout=60 loadfactor=1
    BalancerMember http://new.frontend2.ip:80 timeout=60 loadfactor=1
    ProxySet lbmethod=byrequests
</Proxy>

Once the stats verify that the new env isn’t hitting any firewall or load issue, the loadfactor can be updated (only need to graceful apache) to ramp up traffic so that everything is hitting the new env. Of course, it adds one extra hop for serving requests, but it’s then much safer to switch the DNS entries when you *know* your new system is already handling the production traffic.


Filed under: Uncategorized

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150714 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

We have rebased the master-next branch of our Wily kernel to 4.1 and are
working through fixing up kernel test failures as well as failing DKMS
packages with this newer kernel. We continue to track the 4.2 kernel in
our unstable repo.
—–
Important upcoming dates:

  • https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
    Thurs July 30 – Alpha 2 (~2 weeks away)
    Thurs Aug 6 – 14.04.3 (~3 weeks away)
    Thurs Aug 20 – Feature Freeze (~5 weeks away)
    Thurs Aug 27 – Beta 1 (~6 weeks away)


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 04-Jul through 25-Jul
    ====================================================================
    03-Jul Last day for kernel commits for this cycle
    05-Jul – 11-Jul Kernel prep week.
    12-Jun – 25-Jul Bug verification; Regression testing; Release
    ** NOTE: This cycle produces the kernel that will be in the 14.04.3
    point release.


Open Discussion or Questions? Raise your hand to be recognized

No open Discussions.

Read more
Corey Bryant

  • smoser to check with Odd_Bloke on status of high priority bug 1461242
  • OpenStack talk submissions are due tomorrow, July 15th
  • Next meeting will be on Jul 21st 16:00:00 UTC in #ubuntu-meeting

Full agenda and log

Read more
Diogo Matsubara

  • Caribou wrote a blog post about curtin/maas customization: http://caribou.kamikamamak.com/2015/06/26/custom-partitioning-with-maas-and-curtin-2/ and is working on a kernel crash dump subordinate charm
  • No meeting actions
  • Next meeting will be on Jul 14th 16:00:00 UTC in #ubuntu-meeting

Full agenda and log

Read more
Robie Basak

The meeting was very short with little that needed discussion.

  • matsubara will be performing SRU verification on bug 1443735 “recordfail false positive causes headless servers to hang on boot by default”.
  • The ODS for Tokyo submission is open.
  • No meeting actions were assigned.
  • The next meeting will be on Tue Jul 7 16:00:00 UTC 2015 in #ubuntu-meeting.

Full agenda and log

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150630 Meeting Agenda


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: CVE’s

The current CVE status can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 13-Jun through 04-Jul
    ====================================================================
    12-Jun Last day for kernel commits for this cycle
    14-Jun – 20-Jun Kernel prep week.
    21-Jun – 04-Jul Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

Read more
Shuduo

In case you want to play snappy but don’t have a Raspberry Pi 2 or other hardware…

1, sudo apt-get install virtualbox
2, download snappy image http://cdimage.ubuntu.com/ubuntu-snappy/15.04/20150423/ubuntu-15.04-snappy-amd64-generic.img.xz
3, unxz ubuntu-15.04-snappy-amd64-generic.img.xz
4, VBoxManager convertdd ubuntu-15.04-snappy-amd64-generic.img snappy.vdi –format VDI
5, launch Virtualbox GUI app, create a new VM, OS type is Linux, Version is Ubuntu 64bit, memory is 512MB, Hard driver use an exist virtual hard disk file and select snappy.vdi we just converted from img file.
6, in Settings->Network, change Network Adapter from NAT to Bridged Adapter
7, Start VM, you can use browser to access Snappy App Store by url “webdm.local:4200” or login in from console or ssh with username/password ‘ubuntu/ubuntu’ to do anything fun snappy things like update/rollback

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150623 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

Our wily kernel remains rebased on 4.0.5. We have cleaned up some
config discrepancies and will plan to upload to our
canonical-kernel-team ppa today. We’ll the hopefully get that copied
out to the archive sometime this week or next. Also, with 4.1 final
having just been release, we’ll get our master branch in
git://kernel.ubuntu.com/ubuntu/unstable.git rebased. We will then plan
on rebasing Wily to 4.1 and uploading as well.
—–
Important upcoming dates:

  • https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
    Thurs June 25 – Alpha 1 (~2 days away)
    Thurs July 30 – Alpha 2 (~5 weeks away)


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 13-Jun through 04-Jul
    ====================================================================
    12-Jun Last day for kernel commits for this cycle
    14-Jun – 20-Jun Kernel prep week.
    21-Jun – 04-Jul Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Michael

I tend to do all my work in the cloud (and work physically from a useful but comparatively powerless chromebook running Ubuntu). So creating a Mir Snap on my local machine wasn’t an option I was keen to try.

Mainly for my own documentation, the first attempt at creating a Mir snap (a display server for experimenting with Kodi on Ubuntu Snappy), went like this:

First spin up an Ubuntu Wily development instance in a(ny) openstack cloud (I’m using a Canonical internal one):

$ nova boot --flavor cpu2-ram4-disk100-ephemeral20 --image 1461273c-af73-4839-9f64-3df00446322a --key-name ******** wily_dev

Less than a minute later, ssh in and use the existing snappy packaging branch for mir:


$ sudo add-apt-repository ppa:snappy-dev/tools
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install snappy-tools bzr cmake gcc-multilib ubuntu-snappy-cli mir-demos mir-graphics-drivers-desktop dpkg-dev

$ bzr branch lp:~mir-team/mir/snappy-packaging && cd snappy-packaging && make

The last step uses deb2snap to create the snap package from the installed deb packages. So, the (76M) snap is for the amd64 architecture – as the instance I created is amd64:


$ ls -lh mir_snap1_amd64.snap
-rw-rw-r-- 1 ubuntu ubuntu 76M Jun 21 11:20 mir_snap1_amd64.snap

Next up… using either QEMU or an ARM cloud instance (I’m not sure that the latter is available) to create an ARM Mir snap for my Raspberry Pi, and testing it out…


Filed under: Uncategorized

Read more
Shuduo

1, components on the desk
Image and video hosting by TinyPic

2, bag
Image and video hosting by TinyPic

3, assembling
Image and video hosting by TinyPic

4, and…
Image and video hosting by TinyPic

5, and…
Image and video hosting by TinyPic

6, piglow plugged
Image and video hosting by TinyPic

7, finish
Image and video hosting by TinyPic

8, Ubuntu Sanppy is running.. \o/
Image and video hosting by TinyPic

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150616 Meeting Agenda


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

Our wily kernel remains rebased on 4.0.5. We have uploaded but are
planning to land some additional config changes before we have the
kernel promoted out of wily-proposed. Stay tuned. We have also moved
to tracking 4.1-rc8 on our master branch in
git://kernel.ubuntu.com/ubuntu/unstable.git . We will plan to rebase
Wily to 4.1 final once available.
o/
—–
Important upcoming dates:
– https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
Thurs June 25 – Alpha 1 (~1 week away)
Thurs July 30 – Alpha 2 (~6 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Prep
  • Trusty – Prep
  • Utopic – Prep
  • Vivid – Prep

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 13-Jun through 04-Jul
    ====================================================================
    12-Jun Last day for kernel commits for this cycle
    14-Jun – 20-Jun Kernel prep week.
    21-Jun – 04-Jul Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Michael

orange-matchboxI just received an Orange Matchbox today – a Raspberry Pi 2B with a PiGlow and Ubuntu-engraved casing – to try out Snappy Ubuntu.

As a first project, I want to see if it’s possible to get Kodi (formally XBMC) packaged as a snap. I’m not yet sure if this is possible, but the plan is to install Ubuntu on a separate microSD and setup deb2snap and see whether I can create a snap (minus certain dependencies). Obviously then install the snap on my snappy microSD and profit! (The devel’s in the details of course.)

I’m not sure that deb2snap will work with Ubuntu Trusty (the default image for RPi2), as it was recently announced that XMir will no longer be supported for anything less than Wily. We’ll see how it goes.

I already found and reported my first issue while testing snappy on a VM last week, which got fixed for todays stable release. Let the fun begin…


Filed under: Uncategorized

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150609 Meeting Agenda


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

We have rebased wily to 4.0.5 and have uploaded to the archive. We are
investigating a build failure for ppc64el, but the other arch’s appear
to be building cleanly. Please test and let us know your results. We
will move to start tracking 4.1 on our master-next branch.
—–
Important upcoming dates:
https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
Thurs June 25 – Alpha 1 (~2 weeks away)
Thurs July 30 – Alpha 2 (~7 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 23-May through 13-Jun
    ====================================================================
    22-May Last day for kernel commits for this cycle
    24-May – 30-May Kernel prep week.
    31-May – 13-Jun Bug verification; Regression testing; Release


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

20150602 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

We are still tracking the 4.0.x stable series on wily master-next.
We remain rebased to 4.0.4 and still sorting DKMS testing. We
will continue to shoot for an official upload to Wily in the next few
weeks. Tracking of the 4.1 series is taking place in our unstable git
repo on kernel.ubuntu.com.
—–
Important upcoming dates:
https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule
Thurs June 25 – Alpha 1 (~3 weeks away)
Thurs July 30 – Alpha 2 (~8 weeks away)


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 23-May through 13-Jun
    ====================================================================
    22-May Last day for kernel commits for this cycle
    24-May – 30-May Kernel prep week.
    31-May – 13-Jun Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
LaMont Jones

Once a process is running under apparmor, changing the profile is as simple as updating the profile and reloading it.  Initially getting it into apparmor normally requires a restart, but sometimes you just don’t want to restart the daemon.

The situation

Lets say that you’ve deployed a production service and managed to not actually enable the apparmor profile that you wrote for it.  Now you want to enable it without a restart, since a restart would be disruptive (and would involve admitting that you didn’t actually deploy it under apparmor like you claimed…)

In order to have a binary name for use in our example, let’s call our program “/usr/sbin/inspircd”.  Throughout the following text, my input is in red.

Steps:

Create the apparmor profile and make it active

(Actually creating the profile is beyond the scope of this process.)

apparmor_parser -r /etc/apparmor.d/usr.sbin.inspircd.

Make sure we have gdb

apt-get install gdb

Find the process

ps auxf | grep /usr/sbin/inspircd

(For our example, we will use pid 22143)

Confine the process

If we could do this from outside of the process, this would be trivial.  Then again, there are sound reasons for why only the process itself is permitted to change its profile.

What we want to do here is call: aa_change_profile(“/usr/sbin/inspircd”) from within the process, but it is nearly certain that aa_change_profile is not in the symbol table for our daemon.  So we do it the hard way, by doing what aa_change_profile does: write a particular string to /proc/self/attr/current (the 32 in the write call is the length of the string: no trailing null is needed.)

(Note that while we are in gdb, the process is stopped in the debugger, and users might tend to notice this… I pasted all 5 lines of text into the debugger, which meant that I was stopped in the debugger for under 2 seconds.)

# gdb -p 22143
...
(gdb) call open("/proc/self/attr/current",2)
$1 = 13
(gdb) call write($1,"changeprofile /usr/sbin/inspircd",32)
$2 = 32
(gdb) call close($1)
$3 = 0
(gdb) q
A debugging session is active.

 Inferior 1 [process 22143] will be detached.

Quit anyway? (y or n) y
Detaching from program: /usr/sbin/inspircd, process 22143
#

And now we have a happily confined process, no file descriptors leaked, no daemon restart, and only a second or so of interruption masquerading as lagginess.

Read more
LaMont Jones

Hello world!

Welcome to Canonical Voices. This is your first post. Edit or delete it, then start blogging!

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150526 Meeting Agenda


Release Metrics and Incoming Bugs

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

  • http://kernel.ubuntu.com/reports/kt-meeting.txt


Status: Wily Development Kernel

We are still tracking the 4.0.x stable series on wily master-next.
We’re currently rebased to 4.0.4 and still sorting DKMS testing. We
will shoot for an official upload to Wily in the next few weeks.
Tracking of the 4.1 series is taking place in our unstable git repo on
kernel.ubuntu.com.
—–
Important upcoming dates:
I’ll pull out relevant dates for next week’s meeting.


Status: CVE’s

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

  • http://kernel.ubuntu.com/reports/kernel-cves.html


Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Prep
  • Trusty – Prep
  • Utopic – Prep
  • Vivid – Prep

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    cycle: 23-May through 13-Jun
    ====================================================================
    22-May Last day for kernel commits for this cycle
    24-May – 30-May Kernel prep week.
    31-May – 13-Jun Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

Read more