FWN/Beats/Announcements: Difference between revisions

Revision as of 12:12, 5 October 2009

Announcements

In this section, we cover announcements from the Fedora Project^[1] ^[2] ^[3].

Contributing Writer: Rashadul Islam

THE BREAKING news (Fedora 12 (Constantine) related) are as follows:

FEDORA ANNOUNCE LIST

Reminder: Fedora Board IRC meeting 1600 UTC 2009-10-01

Paul W. Frields announced,"The Board is holding its monthly public meeting on Thursday, October 1, 2009, at 1600 UTC on IRC Freenode.^[1]"

↑ http://www.redhat.com/archives/fedora-announce-list/2009-September/msg00009.html

FEDORA DEVELOPMENT ANNOUNCEMENTS

Final Review of Incomplete Fedora 12 Features

John Poelstra announced,^[1]

"With the passing of Beta Freeze we are now at the point in our release process where we expect all features to be at 100% completion. After requesting status updates, including direct email to the feature owners, the following feature pages do not have a current status.

^[2] ^[3] ^[4] ^[5]

In accordance with our recorded policy of requiring that all features be at 100% at Beta Freeze, I am proposing these features for your review to determine what their disposition should be. ^[6]"

Buyer Beware: A Major Change in NFS is about to happen

Steve Dickson announced as follows,^[1]

As part of the NFSv4 Default ^[2] feature I am one commit away from changing the default protocol version NFS will be using (or at least trying to use).

What does this means to you? Hopefully nothing! In theory this should be a very seamless transition but with all new technology there will be (and are) some rough spots.

Why are make the change? See the NFSv4Default wiki for details, but in a nutshell:

    Better performance - V4 is now a stateful protocol. Meaning the server keeps 
     state on all the clients access a particular file or directory. This
     allows the server to give out delegations (or leases) which in turn
     allows the client to aggressive cache both data and meta data locally

    Firewall Friendly- With v4 only one port is used 2049 for all traffic
     including mounting and file locking.

    Finally it enables us use upcoming minor releases of the the protocol. 
     NFS version 4.1 and pNFS are two example of upcoming minor releases.

FYI, V4 was introduced in Fedora Core 2 so it has been around for a while. I personally have been using it for my home directory for a couple years now.. For more of the nitty gritty details see

   http://www.iaps.com/NFSv4-new-features.html

That's the good news... Here is the bad....

Because the mount command will try NFS v4 first, mounts to older Linux servers will start failing. This is due to a defect in the Linux server exporting code, which is fixed in F-12, *but* there are a number of workarounds

On the server (Which is suggested):

  Add the following entry to the /etc/exports file:
    / *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.

On the client, go back to v3 mounts by doing one of the following:

   Add -o v3 to command line, similar to:
       mount linux-server:/export /mnt

   Change the default mount version in the new /etc/nfsmount.conf file by 
    uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
    See nfsmount.conf(5) man page for details. The diff would look like:

       --- /etc/nfsmount.conf	2009-09-29 16:58:13.000000000 -0400
       +++ /tmp/nfsmount.conf	2009-09-29 16:56:04.000000000 -0400
       @@ -29,7 +29,7 @@
        # options that can be applied on all NFS mount.
        #
        # Protocol Version [2,3,4]
       -#Nfsvers=3
       +Nfsvers=3
        # Network Transport [Udp,Tcp,Rdma]
        # Proto=Tcp
        #

Fedora 12 Freeze at 0600~ 2009-09-30 UTC

Jesse Keating briefly announced, "Just a reminder that the Fedora 12 freeze will be happening tonight at 0600 2009-09-30 UTC, just prior to the rawhide compose tonight. The rawhide for 20090930 will be built from frozen content. You do not need to send tag requests until after that.^[1]"

↑ http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00012.html

Re: CVS Outage Notification - 2009-09-29 04:25 UTC

"It was pointed out to me that many of the packages starting with "a" were not properly branched. I've restarted the branch run for the "a" packages, however this time email will go out for the branch events, and this won't incur another outage. The branching of "a" packages should be done in 10 or 15 minutes.^[1] ", replied Jesse Keating.

↑ http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00011.html

FEDORA EVENTS

Mark your agenda with the following events. Please, consider attending or volunteering at an event near you!

Upcoming Events

North America (NA)^[1] Central & South America (LATAM) ^[2] Europe, Middle East, and Africa (EMEA)^[3] India, Asia, Australia (India/APJ)^[4]

Past Events

Archieve of Past Fedora Events^[1]

↑ http://fedoraproject.org/wiki/Events#Past_Events

[1] ttp://www.redhat.com/archives/fedora-announce-list/

[2] ttp://www.redhat.com/archives/fedora-devel-announce/

[3] ttp://fedoraproject.org/wiki/Events

[4] ttp://www.redhat.com/archives/fedora-announce-list/2009-September/msg00009.html

[5] ttp://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00000.html

[6] ttps://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00008.html

[7] ttps://fedoraproject.org/wiki/Features/DisplayPort

[8] ttps://fedoraproject.org/wiki/Features/LowerProcessCapabilities

[9] ttps://fedoraproject.org/wiki/Features/NFSv4Default

[10] ttps://fedoraproject.org/wiki/Features/Policy/Dropping

[11] ttp://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00013.html

[12] ttps://fedoraproject.org/wiki/Features/NFSv4Default

[13] ttp://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00012.html

[14] ttp://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00011.html

[15] ttp://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29

[16] ttp://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2

[17] ttp://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3

[18] ttp://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4

[19] ttp://fedoraproject.org/wiki/Events#Past_Events

[1]

[2]

[3]

[1]

[1]

[2]

[3]

[4]

[5]

[6]

[1]

[2]

[1]

[1]

[1]

[2]

[3]

[4]

[1]

@@ Line 12: / Line 12: @@
 '''THE BREAKING news (Fedora 12 (Constantine) related) are as follows''':
-==FEDORA ANNOUNCE LIST==
+===FEDORA ANNOUNCE LIST===
 ===Reminder: Fedora Board IRC meeting 1600 UTC 2009-10-01===
@@ Line 20: / Line 20: @@
 <references/>
-==FEDORA DEVELOPMENT ANNOUNCEMENTS==
+===FEDORA DEVELOPMENT ANNOUNCEMENTS===
-===Final Review of Incomplete Fedora 12 Features===
+====Final Review of Incomplete Fedora 12 Features====
 John Poelstra announced,<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00000.html</ref>
@@ Line 37: / Line 37: @@
 <references/>
-===Buyer Beware: A Major Change in NFS is about to happen===
+====Buyer Beware: A Major Change in NFS is about to happen====
 Steve Dickson announced as follows,<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00013.html</ref>
@@ Line 50: / Line 50: @@
 Why are make the change? See the NFSv4Default wiki for details,
 but in a nutshell:
-    * Better performance - V4 is now a stateful protocol. Meaning the server keeps
+     Better performance - V4 is now a stateful protocol. Meaning the server keeps
        state on all the clients access a particular file or directory. This
        allows the server to give out delegations (or leases) which in turn
        allows the client to aggressive cache both data and meta data locally
-    * Firewall Friendly- With v4 only one port is used 2049 for all traffic
+     Firewall Friendly- With v4 only one port is used 2049 for all traffic
        including mounting and file locking.
-    * Finally it enables us use upcoming minor releases of the the protocol.
+     Finally it enables us use upcoming minor releases of the the protocol.
        NFS version 4.1 and pNFS are two example of upcoming minor releases.
@@ Line 70: / Line 70: @@
 Because the mount command will try NFS v4 first, mounts to older Linux servers
-will start failing like:
+will start failing.
- # mount linux-server:/export /mnt
- mount.nfs: mounting linux-server:/export failed, reason given by server:
-    No such file or directory
 This is due to a defect in the Linux server exporting code, which is fixed
 in F-12, *but* there are a number of workarounds
 On the server (Which is suggested):
-    * Add the following entry to the /etc/exports file:
+    Add the following entry to the /etc/exports file:
       / *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.
 On the client, go back to v3 mounts by doing one of the following:
-   * Add -o v3 to command line, similar to:
+    Add -o v3 to command line, similar to:
          mount linux-server:/export /mnt
-   * Change the default mount version in the new /etc/nfsmount.conf file by
+    Change the default mount version in the new /etc/nfsmount.conf file by
       uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
       See nfsmount.conf(5) man page for details. The diff would look like:
@@ Line 105: / Line 100: @@
 <references/>
-===Fedora 12 Freeze at 0600~ 2009-09-30 UTC===
+====Fedora 12 Freeze at 0600~ 2009-09-30 UTC====
 Jesse Keating briefly announced, "Just a reminder that the Fedora 12 freeze will be happening tonight at
 2009-09-30 UTC, just prior to the rawhide compose tonight.  The
@@ Line 113: / Line 108: @@
 <references/>
-===Re: CVS Outage Notification - 2009-09-29 04:25 UTC===
+====Re: CVS Outage Notification - 2009-09-29 04:25 UTC====
 "It was pointed out to me that many of the packages starting with "a"
 were not properly branched.  I've restarted the branch run for the "a"
@@ Line 123: / Line 118: @@
 <references/>
-==FEDORA EVENTS==
+===FEDORA EVENTS===
 Mark your agenda with the following events. Please, consider attending or volunteering at an event near you!
-===Upcoming Events===
+====Upcoming Events====
-    * North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29</ref>
+North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29</ref>
-    * Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2</ref>
+Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2</ref>
-    * Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3</ref>
+Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3</ref>
-    * India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4</ref>
+India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4</ref>
 <references/>
-===Past Events===
+====Past Events====
 Archieve of Past Fedora Events<ref>http://fedoraproject.org/wiki/Events#Past_Events</ref>
 <references/>

Search